March 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 17 Mar '21

17 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 Radoslav Tzvetkov <rtsvetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1179863 -- 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 1183618] New: Module e1000e appears to be unsigned
by bugzilla_noreply＠suse.com 16 Mar '21

16 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183618 Bug ID: 1183618 Summary: Module e1000e appears to be unsigned Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: millermj4(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: After upgrading to kernel 5.3.18-lp152.66-default, I lost my ethernet connection. $ sudo /sbin/modprobe e1000e results in the message "modprobe: ERROR: could not insert 'e1000e': Operation not permitted" and dmesg contains the error "Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7" Reproducible: Always Steps to Reproduce: 1. YAST >> hardware >> Network card >> ethernet connections >> drivers >> modules says the the module name is e1000e 2. Run sudo /sbin/modprobe e1000e Actual Results: 1. Get terminal message "modprobe: ERROR: could not insert 'e1000e': Operation not permitted" 2. Message at end of dmesg is "Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7" Expected Results: Module would be loaded. $ ip a would show an ethernet entry SysRq-x produces the following message in dmseg: sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) dump-ftrace-buffer(z) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1183132] New: Kernel wont boot after grub initialization 5.11.2
by bugzilla_noreply＠suse.com 16 Mar '21

16 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183132 Bug ID: 1183132 Summary: Kernel wont boot after grub initialization 5.11.2 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After a successful update and reboot, i was unable to load opensuse tumbleweed after grub initialization. after trying to load the kernel, it hung at that point, then about 3-5 minutes later it rebooted all by itself without user input. this is to do with the current 5.11.2 kernel. kernels before this had no issues with booting. i have had to reboot into a snapshot earlier than last update. -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1183198] New: Kernel 5.11.2: self-compiled module fails to load with relocation error
by bugzilla_noreply＠suse.com 16 Mar '21

16 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183198 Bug ID: 1183198 Summary: Kernel 5.11.2: self-compiled module fails to load with relocation error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Stromeko(a)NexGo.DE QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The latest kernel update changes something that makes the BMP280 driver fail when trying to instantiate a device: Mar 07 09:53:29 Otto kernel: i2c i2c-1: new_device: Instantiated device bme280 at 0x76 Mar 07 09:53:29 Otto kernel: module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000ce203c91, val ffffffffc106808a One of the suggestions floating around for possible causes of this error is a mismatch of the headers/sources witth the currently loaded kernel. I'm using the source packages supplied with that exact same kernel version, so that should not happen. The error happens identically both when pre-compiling the module under the old (booted) kernel for the new one or when compiling the module under the new kernel. The message doesn't change between reboots either. It was happily working from around one year ago (when I attached the sensor) up until the previous kernel 5.10.16 and it continues to work with the previous kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1183132] Kernel wont boot after grub initialization 5.11.2
by bugzilla_noreply＠suse.com 16 Mar '21

16 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183132 https://bugzilla.suse.com/show_bug.cgi?id=1183132#c23 Joerg Roedel <jroedel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jroedel(a)suse.com) | --- Comment #23 from Joerg Roedel <jroedel(a)suse.com> --- I wrote a couple of fixes for this issue and prepares a kernel which includes them. Please find it here: https://download.opensuse.org/repositories/home:/joro:/tw-iommu-fixes/stand… Can you please test this kernel and report back whether it fixes the boot failures? -- 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 16 Mar '21

16 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c26 --- Comment #26 from Michal Suchanek <msuchanek(a)suse.com> --- Then this is upstream problem and we don't have a fix. -- 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 1169099] [Build 20200405][aarch64] crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore
by bugzilla_noreply＠suse.com 16 Mar '21

16 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c25 --- Comment #25 from Petr Cervinka <pcervinka(a)suse.com> --- Not yet https://openqa.opensuse.org/tests/1662563#step/kdump_and_crash/58 -- 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 1169099] [Build 20200405][aarch64] crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore
by bugzilla_noreply＠suse.com 16 Mar '21

16 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c24 --- Comment #24 from Michal Suchanek <msuchanek(a)suse.com> --- Is this fixed in Factory? -- 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 1183132] Kernel wont boot after grub initialization 5.11.2
by bugzilla_noreply＠suse.com 16 Mar '21

16 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1183132 https://bugzilla.suse.com/show_bug.cgi?id=1183132#c22 --- Comment #22 from Joerg Roedel <jroedel(a)suse.com> --- (In reply to Takashi Iwai from comment #18) > OK, now I took a deeper look at the picture in comment 8, and it indicates > some bug in AMD iommu stuff. > > Joerg, could you check it? As far as I read, it's in the line > iommu = amd_iommu_rlookup_table[devid]; > in irq_remapping_select(). It's not about the !amd_iommu_irq_remap check, > which should have been there. Okay, this would make sense. The irq_remapping_select() function was added in 5.11, so the regression can be there. I will have a look. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183554] New: Can't boot into desktop with AMD card
by bugzilla_noreply＠suse.com 16 Mar '21

16 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183554 Bug ID: 1183554 Summary: Can't boot into desktop with AMD card Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: thomas.wihl(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 847244 --> http://bugzilla.opensuse.org/attachment.cgi?id=847244&action=edit dmesg output Since kernel 5.11.x I can no longer start a desktop session. I get to the login screen and when using Wayland the system instantly hangs. When selecting X11 I get a few minutes before the system hangs. If I remove the Radeon RX 480 card everything is fine. Kernel 5.10.x worked fine, but nether 5.11.2, 5.11.4, 5.12-RC2 are able to start the desktop. There are quite some bugs with the new kernel, but I couldn't find one similar to mine. -- You are receiving this mail because: You are the assignee for the bug.

1 10