April 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

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

14 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c31 --- Comment #31 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: toolchain_zypper https://openqa.suse.de/tests/5814266 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 1181862] GCC 11: kernel-default package failures
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1181862 https://bugzilla.suse.com/show_bug.cgi?id=1181862#c31 --- Comment #31 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:1177-1: An update that solves 21 vulnerabilities and has 74 fixes is now available. Category: security (important) Bug References: 1152472,1152489,1153274,1154353,1155518,1156256,1159280,1160634,1167773,1168777,1169514,1169709,1171295,1173485,1177326,1178163,1178330,1179454,1180197,1180980,1181383,1181674,1181862,1182011,1182077,1182485,1182552,1182574,1182591,1182595,1182715,1182716,1182717,1182770,1182989,1183015,1183018,1183022,1183023,1183048,1183252,1183277,1183278,1183279,1183280,1183281,1183282,1183283,1183284,1183285,1183286,1183287,1183288,1183366,1183369,1183386,1183412,1183416,1183427,1183428,1183445,1183447,1183501,1183509,1183530,1183534,1183540,1183593,1183596,1183598,1183637,1183646,1183662,1183686,1183692,1183696,1183750,1183757,1183775,1183843,1183859,1183871,1184167,1184168,1184170,1184176,1184192,1184193,1184196,1184198,1184217,1184218,1184219,1184220,1184224 CVE References: CVE-2019-18814,CVE-2019-19769,CVE-2020-27170,CVE-2020-27171,CVE-2020-27815,CVE-2020-35519,CVE-2021-27363,CVE-2021-27364,CVE-2021-27365,CVE-2021-28038,CVE-2021-28375,CVE-2021-28660,CVE-2021-28688,CVE-2021-28964,CVE-2021-28971,CVE-2021-28972,CVE-2021-29264,CVE-2021-29265,CVE-2021-29647,CVE-2021-3428,CVE-2021-3444 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP2 (src): kernel-azure-5.3.18-18.41.1, kernel-source-azure-5.3.18-18.41.1, kernel-syms-azure-5.3.18-18.41.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 1184578] kernel-syms package pulls in kernel-preempt-devel to satisfy dependencies
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184578 https://bugzilla.suse.com/show_bug.cgi?id=1184578#c2 --- Comment #2 from David Hodgson <admin(a)different-perspectives.com> --- OK, so, to be clear: either DKMS is pulling in the wrong meta-package to be able to build the necessary kernel modules for the running system, or there's a philosophical difference between what's required and what's recommended in kernel-syms. As I see it, the majority of people using DKMS only want to build modules for their running system, so any other kernel-whatever-devel packages required are just clutter, kibble. I'll transfer as a defect against DKMS. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184650] Kernel:HEAD should use tilde instead of dot/dash for version
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184650 https://bugzilla.suse.com/show_bug.cgi?id=1184650#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- The fix was pushed to packaging/for-next branch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184653] System fails to boot with kernel 5.3.18-52-default
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184653 https://bugzilla.suse.com/show_bug.cgi?id=1184653#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |franzmach(a)yahoo.de, | |tiwai(a)suse.com Flags| |needinfo?(franzmach(a)yahoo.d | |e) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you test with the kernel in OBS Kernel:SLE15-SP3 repo? Just to be sure whether it's an issue that has been already fixed in the git repo. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184671] openrazer drivers aren't automatically rebuilt for new kernel or their own updates
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184671 https://bugzilla.suse.com/show_bug.cgi?id=1184671#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Assignee|kernel-bugs(a)opensuse.org |luca.emanuel.weiss(a)gmail.co | |m --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Reassigned to the corresponding package maintainer. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184671] New: openrazer drivers aren't automatically rebuilt for new kernel or their own updates
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184671 Bug ID: 1184671 Summary: openrazer drivers aren't automatically rebuilt for new kernel or their own updates 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: iqgrande(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0 Build Identifier: Greetings: I use some Razer peripherals and, accordingly, have installed some of the Razer tools for configuring them; the list of items I've installed is below. * openrazer-daemon * openrazer-kernel-modules-dkms * openrazer-meta * polychromatic * python3-openrazer I, basically, followed the instructions to install it here: https://software.opensuse.org/download.html?project=hardware%3Arazer&packag… Anyways, when I update my system, things like the kernel are updated but these packages are not. I update my system with the following commands. Code: {{{ sudo zypper refresh && sudo zypper dup && sudo flatpak update }}} I can see it being out of date because my tray applet indicates the daemon is not working properly and through some sleuthing (see below). Code: {{{ > uname -a Linux babeltumble 5.11.11-1-default #1 SMP Tue Mar 30 17:57:52 UTC 2021 (dbc4a02) x86_64 x86_64 x86_ 64 GNU/Linux > sudo dkms status [sudo] password for root: openrazer-driver, 3.0.0, 5.11.6-1-default, x86_64: installed }}} The only way I've found to get this to update is to do the following. Code: {{{ sudo dkms remove -m openrazer-driver -v 3.0.0 -k 5.11.6-1-default sudo dkms autoinstall }}} I am new to openSUSE Tumbleweed and absolutely love it. Is this driver something I need to continue manually updating or is there a method for it to automatically update when new kernels are installed? Thank you for any insight you can provide into this. I did a bunch of searches and couldn't find anything to discuss this; I apologize if I missed something. These drivers were updated recently however the new versions were not automatically built against the current kernel. This also shows that the upgrade does not clean up the older version and makes the upgrade more difficult (see below). So, ultimately, I currently have the 5.11.6-1-default kernel built with version 3.0.0 of these drivers, while version 5.11.11-1-default of the kernel and 3.0.1-1.1 of the drivers are actually installed. Code: {{{ > sudo zypper search -s razer [sudo] password for root: Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+-------------------------------+------------+-----------+--------+---------------------- i | openrazer-daemon | package | 3.0.1-1.1 | noarch | hardware:razer i | openrazer-kernel-modules-dkms | package | 3.0.1-1.1 | noarch | hardware:razer i+ | openrazer-meta | package | 3.0.1-1.1 | noarch | hardware:razer | openrazer-meta | srcpackage | 3.0.1-1.1 | noarch | hardware:razer i | python3-openrazer | package | 3.0.1-1.1 | noarch | hardware:razer | razercfg | package | 0.41-1.9 | x86_64 | Main Repository (OSS) | razercfg | package | 0.41-1.9 | x86_64 | openSUSE:Factory | razercfg | package | 0.41-1.9 | x86_64 | openSUSE:Tumbleweed | razercfg | package | 0.41-1.9 | i586 | Main Repository (OSS) | razercfg | package | 0.41-1.9 | i586 | openSUSE:Factory | razercfg | package | 0.41-1.9 | i586 | openSUSE:Tumbleweed | razergenie | package | 0.9.0-2.6 | x86_64 | hardware:razer | razergenie | package | 0.9.0-2.6 | i586 | hardware:razer | razergenie | srcpackage | 0.9.0-2.6 | noarch | hardware:razer | razergenie-debuginfo | package | 0.9.0-2.6 | x86_64 | hardware:razer | razergenie-debuginfo | package | 0.9.0-2.6 | i586 | hardware:razer | razergenie-debugsource | package | 0.9.0-2.6 | x86_64 | hardware:razer | razergenie-debugsource | package | 0.9.0-2.6 | i586 | hardware:razer > sudo dkms status Error! Could not locate dkms.conf file. File: /var/lib/dkms/openrazer-driver/3.0.0/source/dkms.conf does not exist. }}} Kind regards, Anthony Reproducible: Always Steps to Reproduce: 1. Install openrazer-meta stuff on site given in details. 2. When kernel or drivers are updated (i.e., a newer version is installed), the kernel mod will not be automatically generated with the new items and, as such, the drivers won't be loaded. 3. Actual Results: The kernel modules are not loaded. Expected Results: I would've expected these kernel modules to be updated as both the kernel or the drivers themselves that create them are updated. I am new to openSUSE so I am perhaps missing something in terms of expectations. I think everything is covered in "details". -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184403] iwlwifi driver failing to load in current MicroOS Desktop image
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184403 http://bugzilla.opensuse.org/show_bug.cgi?id=1184403#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- The soft-dependency installation only for the hardware (but no Recommends) can be achieved via zypper inr --no-recommends And I'm sure that you'd need more and more different firmware files as long as you run on various machines. e.g. AMD GPU mandates the firmware (otherwise you'll get only blank screen) and CPU microcode is a must for the security mitigations. Lost of BT devices need the firmware files, etc, etc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184403] iwlwifi driver failing to load in current MicroOS Desktop image
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184403 http://bugzilla.opensuse.org/show_bug.cgi?id=1184403#c14 --- Comment #14 from Dario Faggioli <dfaggioli(a)suse.com> --- (In reply to Takashi Iwai from comment #13) > (In reply to Dario Faggioli from comment #12) > > Totally agree. What I still don't know (and am trying to figure out) is > > where it is decided what will end up in the install media. > > > > Like, using this issue as an example, why isn't the firmware package there? > > If it's due to the no-recommends thing... Where is it that we set > > "no-recommends" in such a way that is has this effect? > > > > Is it, perhaps, here: > > https://github.com/yast/skelcd-control-MicroOS/blob/master/control/control. > > MicroOS.xml#L100 ? > > Hm, patterns-microos-onlyDVD seems containing kernel-firmware. It looks > specific to MicroOS, so I don't know what's the purpose, though... > Yeah, it really is. > In the normal installation, kernel-firmware is chosen either via the > recommends from kernel-default (or equivalent), or from patterns-media, as > far as I look though the packages So, install-recommends is mandatory in > that case. > We've been discussing (on MicroOS Desktop chat channels) how to deal with this. Enabling soft dependencies is apparently a no go, nor we want firmware-all in there. So I'll probably add the most obvious network firmware packages to the onlyDVD pattern (which definitely includes iwlwifi) and see if this fixes this issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184575] kernel 5.3.18-lp152.69-default does not boot
by bugzilla_noreply＠suse.com 13 Apr '21

13 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184575 https://bugzilla.suse.com/show_bug.cgi?id=1184575#c35 --- Comment #35 from Takashi Iwai <tiwai(a)suse.com> --- For the people who can boot with intel_iommu=off boot option, please go to bug 1184585. The culprit was identified and the test fix kernel is being built there. If your machine doesn't boot with intel_iommu=off boot option, this must be a different bug, and we'd like to see whether other options make boot forward (even if not fully functional). If that's the case, please speak up. -- You are receiving this mail because: You are the assignee for the bug.

1 0