October 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1191229] [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 05 Oct '21

05 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191229 https://bugzilla.suse.com/show_bug.cgi?id=1191229#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek(a)suse.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Hrm, I failed to find where the problem lies. Is the line 130 of kernel-source.spec %obsolete_rebuilds %name ?? This is expanded in rpm/kernel-spec-macros as %define obsolete_rebuilds() %( %{verbose:set -x} \ set -- $(echo %release | sed -rn 's/(.*\\.)([0-9]+)($|\\.[^.]*[^.0-9][^.]*$)/\\1 \\2 \\3/p') \ if test -n "$2" && test "$2" -gt 99; then echo "warning: Rebuild counter too high in %release" >&2; exit 0; fi \ seq 1 $(($2-1)) | sed "s/.*/Obsoletes: %1 = %version-$1&$3/" \ ) In anyway adding Michal to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 05 Oct '21

05 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c19 --- Comment #19 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2021:3203-2: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1189537,1190190 CVE References: JIRA References: Sources used: SUSE MicroOS 5.1 (src): kmod-29-4.9.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189537] SLE15-SP3 modinfo doesn't show module signature properly
by bugzilla_noreply＠suse.com 05 Oct '21

05 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1189537 https://bugzilla.suse.com/show_bug.cgi?id=1189537#c17 --- Comment #17 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2021:3203-2: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1189537,1190190 CVE References: JIRA References: Sources used: SUSE MicroOS 5.1 (src): kmod-29-4.9.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191260] kernel 5.14.8 post scriptlets failing
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191260 https://bugzilla.suse.com/show_bug.cgi?id=1191260#c12 --- Comment #12 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #11) > > By definition, cert-script is a noop on systems that don't support UEFI. > > We have secure boot on s390 and support for POWER is in progress (expected > in 15 SP5). Maybe the kernel makes this look like EFI to userspace but the > expectation is that we will have a different tool for POWER eventually. Fine. Either s390x and Power will use mokutil, in which case the test will be correct. Or they will use some other tool, in which we'll need to extend the test. It's fine both ways, and actually easier to maintain than having the same test in multiple places in the code. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c9 --- Comment #9 from Andrea P <pandre.x(a)gmail.com> --- I finally made it, thanks :) > > It's /usr/sbin/alsa-info.sh included in alsa-utils package. It should have > been already installed. Just run it as root with --no-upload option, and > attach the generated file to Bugzilla (don't paste, it's big). > Done, I've attached both pre-sleep and post-sleep alsa-info.sh output > > OK, then to make things easier: > - Try to boot with a boot option "3" > This will boot to Linux console without GUI > - Login there, plug USB-audio device, test directly via aplay > % aplay -Dplughw:XXX foo.wav > as mentioned in the above. > - Do suspend/resume > % systemctl suspend > - Check again aplay and confirm the mono output > - Unload / reload the module > % sudo modprobe -r snd-usb-audio > % sudo modprobe snd-usb-audio > - Test aplay again done, I can confirm it sound in mono. Once I try to reboot the usb module, it gives me "Device or resource busy". Please see screenshot attached "rebooting usb module". Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190763] New: Boost does not turn on
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190763 Bug ID: 1190763 Summary: Boost does not turn on Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: matthewweb(a)yandex.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When turned on, boost is not activated on the amd a6 processor. It turns on either when turned on without a battery, or when switching from standby mode. Secure boot disabled. Boost works great on Archlinux, Gentoo, Windows 10 https://susepaste.org/15334819(dmesg) https://susepaste.org/41933786(inxi) -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c8 --- Comment #8 from Andrea P <pandre.x(a)gmail.com> --- Created attachment 852922 --> http://bugzilla.opensuse.org/attachment.cgi?id=852922&action=edit rebooting usb module -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c7 --- Comment #7 from Andrea P <pandre.x(a)gmail.com> --- Created attachment 852921 --> http://bugzilla.opensuse.org/attachment.cgi?id=852921&action=edit post-sleep alsa.sh -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c6 --- Comment #6 from Andrea P <pandre.x(a)gmail.com> --- Created attachment 852919 --> http://bugzilla.opensuse.org/attachment.cgi?id=852919&action=edit pre-sleep alsa.sh -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191260] kernel 5.14.8 post scriptlets failing
by bugzilla_noreply＠suse.com 04 Oct '21

04 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191260 https://bugzilla.suse.com/show_bug.cgi?id=1191260#c11 --- Comment #11 from Michal Suchanek <msuchanek(a)suse.com> --- (In reply to Martin Wilck from comment #8) > (In reply to Michal Suchanek from comment #7) > > > There are branches that do nothing and branch that complains about wrong > > scriptlet. > > So what? What's the benefit of running the noop branch, or seeing that > complaint on systems where the entire concept of certificates doesn't matter? > > By definition, cert-script is a noop on systems that don't support UEFI. We have secure boot on s390 and support for POWER is in progress (expected in 15 SP5). Maybe the kernel makes this look like EFI to userspace but the expectation is that we will have a different tool for POWER eventually. > Therefore exiting early (and without a warning, which would just confuse > users without good reason) on such a system is the right thing to do. As a > side effect, it makes the code more compact and easier to read. To the contrary - code that exits at random is difficult to follow, and is the very cause of bug 1189841 - if your code does not run because of IFS set at the start of because of a test exiting at the start the result is the same - the code does not run. -- You are receiving this mail because: You are on the CC list for the bug.

1 0