April 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1185403] New: Suspend broken with kernel 5.12 on Lenovo T500
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185403 Bug ID: 1185403 Summary: Suspend broken with kernel 5.12 on Lenovo T500 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: schwab(a)linux-m68k.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is the kernel from Kernel:stable, running on a 15.2 system. Since 5.12.0, suspend is broken, the kernel or the system crashes after: Apr 28 12:34:17 hase systemd[1]: Started TLP suspend/resume. Apr 28 12:34:17 hase systemd[1]: Reached target Sleep. Apr 28 12:34:17 hase systemd[1]: Starting Suspend... Apr 28 12:34:17 hase systemd-sleep[5868]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend Apr 28 12:34:17 hase systemd-sleep[5868]: Suspending system... Apr 28 12:34:17 hase kernel: PM: suspend entry (deep) -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1152773] seccomp error if running containers with podman on armv7
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1152773 https://bugzilla.suse.com/show_bug.cgi?id=1152773#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- SECCOMP_FILTER is available only when CONFIG_OABI_COMPAT=n. It's explicitly limited via commit 9170217510cd280c704966738e7c1660c8fa5cbd ARM: 7888/1: seccomp: not compatible with ARM OABI And kernel-lpae defines this, so CONFIG_SECCOMP_FILTER isn't available there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183265] [Build 20210308] openQA test fails for boot_linuxrc
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183265 http://bugzilla.opensuse.org/show_bug.cgi?id=1183265#c4 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbrugger(a)suse.com Component|Other |Installation Assignee|kernel-bugs(a)opensuse.org |yast2-maintainers(a)suse.de QA Contact|qa-bugs(a)suse.de |jsrain(a)suse.com --- Comment #4 from Matthias Brugger <mbrugger(a)suse.com> --- does not seem to be a kernel bug. Reassigning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185263] Lenovo TP E15 (2nd Gen): Display remains dark when resuming from suspend
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1185263 https://bugzilla.suse.com/show_bug.cgi?id=1185263#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com, | |Ulrich.Windl(a)rz.uni-regensb | |urg.de Flags| |needinfo?(Ulrich.Windl(a)rz.u | |ni-regensburg.de) --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Could you check with openSUSE Leap 15.3 kernel? AMD Renoir support on Leap 15.2 is somewhat limited. And it's possible that the backlight control is broken on AMD driver. At best, check whether the latest upstream kernel works with the kernel package in OBS Kernel:stable repo. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185263] Lenovo TP E15 (2nd Gen): Display remains dark when resuming from suspend
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1185263 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |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

[Bug 1183009] Some armv6/7 builds on OBS fail due to kernel 5.11 modules not being loaded properly
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183009 https://bugzilla.suse.com/show_bug.cgi?id=1183009#c12 --- Comment #12 from Dirk Mueller <dmueller(a)suse.com> --- submitted again to both stable and master branch, as it appears noone merged stable into master before putting it into stable :-(( -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183009] New: Some armv6/7 builds on OBS fail due to kernel 5.11 modules not being loaded properly
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183009 Bug ID: 1183009 Summary: Some armv6/7 builds on OBS fail due to kernel 5.11 modules not being loaded properly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, fvogt(a)suse.com Found By: --- Blocker: --- Since last Factory check-in, which includes kernel upgrade to 5.11, we see some armv6/7 JeOS images build failing with 'mount' which does not know 'vfat' or 'btrfs'. Also, we have some guest kernel traces such as: [ 44s] [ 8.996985] vfat: section 4 reloc 1 sym '_raw_spin_lock': relocation 28 out of range (0xbf00901c -> 0xc101cb28) -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1185332] New: snapshot 20210425 did not include kernel-syms-5.11.16
by bugzilla_noreply＠suse.com 27 Apr '21

27 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185332 Bug ID: 1185332 Summary: snapshot 20210425 did not include kernel-syms-5.11.16 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: timothyadams(a)ymail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just dup'd to snapshot 20210425, and picked "solution 3" from the options below: Problem: kernel-syms-5.11.16-1.1.x86_64 requires kernel-default-devel = 5.11.16-1, but this requirement cannot be provided not installable providers: kernel-default-devel-5.11.16-1.1.i586[download.opensuse.org-oss] Solution 1: deinstallation of kernel-syms-5.11.15-1.2.x86_64 Solution 2: install kernel-default-devel-5.11.16-1.1.i586 despite the inferior architecture Solution 3: keep obsolete kernel-syms-5.11.15-1.2.x86_64 Solution 4: break kernel-syms-5.11.16-1.1.x86_64 by ignoring some of its dependencies On reboot, uname -r says that I'm still on kernel 5.11.15. The relevant output of zypper se - si 'kernel*' says: i+ | kernel-default | package | 5.11.15-1.2 | x86_64 | Main Repository (OSS) i+ | kernel-default-devel | package | 5.11.15-1.2 | x86_64 | Main Repository (OSS) i+ | kernel-devel | package | 5.11.15-1.2 | noarch | (System Packages) i+ | kernel-devel | package | 5.11.16-1.1 | noarch | Main Repository (OSS) i+ | kernel-macros | package | 5.11.16-1.1 | noarch | Main Repository (OSS) i | kernel-source | package | 5.11.15-1.2 | noarch | (System Packages) i | kernel-source | package | 5.11.16-1.1 | noarch | Main Repository (OSS) i+ | kernel-syms | package | 5.11.15-1.2 | x86_64 | (System Packages) Everything seems to work, but I've never seen a new kernel-syms problem like this on arrival of a new kernel, so thought I should file a report. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1185332] snapshot 20210425 did not include kernel-syms-5.11.16
by bugzilla_noreply＠suse.com 27 Apr '21

27 Apr '21

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

1 0

[Bug 1152773] seccomp error if running containers with podman on armv7
by bugzilla_noreply＠suse.com 27 Apr '21

27 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1152773 https://bugzilla.suse.com/show_bug.cgi?id=1152773#c4 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com Component|Containers |Kernel Assignee|containers-bugowner(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #4 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Guillaume GARDET from comment #3) > (In reply to Guillaume GARDET from comment #1) > > armv7 has no seccomp filter since HAVE_ARCH_SECCOMP_FILTER is not selected > > by armv7. Only arm64 selects HAVE_ARCH_SECCOMP_FILTER. > > > > In 2012 some patches were sent to add this support to armv7, but never ended > > in the kernel: > > http://lkml.iu.edu/hypermail/linux/kernel/1210.3/03963.html > > CONFIG_HAVE_ARCH_SECCOMP_FILTER is enabled since > https://github.com/openSUSE/kernel-source/commit/ > e9e55d07c18023edb983e14bacdc2ff2542671c7 > > So, it should be fine now, but it is still broken. It might work using kernel-default meanwhile, but kernel-lpae (and kernel-obs-build, same binary) are missing: CONFIG_HAVE_ARCH_SECCOMP_FILTER=y CONFIG_SECCOMP_FILTER=y Reassigning to kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0