September 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190256 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 1189365] New: NULL deref in __d_lookup_rcu+0x70/0x190
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189365 Bug ID: 1189365 Summary: NULL deref in __d_lookup_rcu+0x70/0x190 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851690 --> http://bugzilla.opensuse.org/attachment.cgi?id=851690&action=edit netconsole log with backtraces I have a server that has been running nicely for a year and now crashed the 3rd time within 10 days. kernel 5.3.18-lp152.84-default BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:__d_lookup_rcu+0x70/0x190 Call Trace: lookup_fast+0x52/0x2d0 walk_component+0x48/0x300 ? path_init+0x192/0x320 path_lookupat+0x6e/0x210 filename_lookup+0xb6/0x190 ? __check_object_size+0xd4/0x1a0 ? strncpy_from_user+0x47/0x180 ? getname_flags+0x66/0x1d0 ? vfs_statx+0x73/0xe0 vfs_statx+0x73/0xe0 ? do_futex+0x17a/0x4c0 __do_sys_newfstatat+0x31/0x70 ? __x64_sys_futex+0x5e/0x1d0 do_syscall_64+0x65/0x1f0 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Interestingly, it also did not auto-reboot with cat /proc/sys/kernel/panic 90 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1189733] Screen flickers and network disconnects when on battery power on Samsung Chromebook3
by bugzilla_noreply＠suse.com 08 Sep '21

08 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189733 https://bugzilla.suse.com/show_bug.cgi?id=1189733#c4 --- Comment #4 from Yitzhak Bar Geva <yitzhakbargeva(a)gmail.com> --- Thanks. Hope I can get to it soon -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190133] Bluetooth no longer working
by bugzilla_noreply＠suse.com 08 Sep '21

08 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190133 https://bugzilla.suse.com/show_bug.cgi?id=1190133#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(gantsevdenis@gmai | |l.com) | --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for confirmation. Let's close now, then. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189596] iwlwifi: BUG: kernel NULL pointer dereference, address: 0000000000000000
by bugzilla_noreply＠suse.com 08 Sep '21

08 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189596 https://bugzilla.suse.com/show_bug.cgi?id=1189596#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- The "unofficial" kernel packages that are freshly built from the latest git branch is found in OBS Kernel:* projects, e.g. for Leap 15.3, it's OBS Kernel:SLE15-SP3. Leap 15.2 has its own branch, so it's in OBS Kernel:openSUSE-15.2, and TW is OBS Kernel:stable repo. Kernel:HEAD contains the built from the latest Linus tree (starting after rc1 release). You can find some more information in https://kernel.suse.com/ Note that the above are unofficial builds, hence they won't boot with Secure Boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189596] iwlwifi: BUG: kernel NULL pointer dereference, address: 0000000000000000
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189596 https://bugzilla.suse.com/show_bug.cgi?id=1189596#c10 --- Comment #10 from Vicente Adolfo Bolea Sanchez <vicente.bolea(a)gmail.com> --- (In reply to Takashi Iwai from comment #9) > The "official" package is in update repo, i.e. > http://download.opensuse.org/update/leap/15.3/sle/x86_64/ > It's in sle/* because Leap 15.3 is composed with multiple layers, and the > kernel is derived from SLE15-Sp3. Good to know, but what I was referring is at the OpenSUSE build service, what I wonder if there is a developing repo/package for kernel-default. This is the equivalent of https://build.opensuse.org/package/show/openSUSE%3AFactory/vim for the vim package. In general, I wonder where are located the OpenSUSE standard repos in the OpenSUSE build service. > As you mentioned that the bug is no longer reproducible with the latest > kernel, I close the entry for now. Feel free to reopen if it's reproduced > again (hopefully reliably). Sure! Nothing to be done, as it is already resolved. Good to have this ticket for the record. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190235] umip: remember that you printed the warning and only print it once
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190235 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |bpetkov(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189674] New: config: enable CONFIG_PRINTK_CALLER
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189674 Bug ID: 1189674 Summary: config: enable CONFIG_PRINTK_CALLER 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: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de CC: pmladek(a)suse.com Depends on: 1189671 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1189671 +++ From Petr Mladek: When on it. Would you like to enable? CONFIG_PRINTK_CALLER=y It adds extra information about the caller into the console/syslog output. It might be used to sort mixed lines. It looks like: [161722.464573] [ T1695] sysrq: Show backtrace of all active CPUs [161722.471152] [ T1695] NMI backtrace for cpu 1 [161722.471163] [ T1695] CPU: 1 PID: 1695 Comm: bash Not tainted 5.14.0-rc1-default+ #276 [161722.471196] [ T1695] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba527-rebuilt.opensuse.org 04/01/2014 [161722.471201] [ T1695] Call Trace: [161722.471218] [ T1695] dump_stack_lvl+0x47/0x60 [161722.471340] [ T1695] nmi_cpu_backtrace+0xf1/0x110 [161722.471403] [ T1695] ? lapic_can_unplug_cpu+0xa0/0xa0 [...] [161722.471793] [ T1695] R13: 0000000000000001 R14: 00007f0d0e9c3720 R15: 0000000000000002 [161722.471864] [ T1695] Sending NMI from CPU 1 to CPUs 0,2-3: [161722.472021] [ C2] NMI backtrace for cpu 2 skipped: idling at native_safe_halt+0xb/0x10 [161722.472061] [ C3] NMI backtrace for cpu 3 skipped: idling at native_safe_halt+0xb/0x10 [161722.472093] [ C0] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xb/0x10 , where "echo l > /proc/sysrq-trigger" was called by the process PID 1695. The backtrace on this CPU was printed in the same context. While the backtrace on the other CPUs were printed in IRQ context of the respective CPU. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1190235] umip: remember that you printed the warning and only print it once
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190235 https://bugzilla.suse.com/show_bug.cgi?id=1190235#c4 --- Comment #4 from Borislav Petkov <bpetkov(a)suse.com> --- Ok, I can't read. It says /* Bursts of 5 messages every two minutes */ static DEFINE_RATELIMIT_STATE(ratelimit, 2 * 60 * HZ, 5); so it is actually every *two* minutes. So it works as advertized (timestampss are every 2 minutes). So, the thing I'm thinking about is adding a "umip=quiet" which you supply at the kernel cmdline and no more output. How's that? [ 115.100225] umip: sidt[2578] ip:55a8f9ecf083 sp:7ffcd9824480: SIDT instruction cannot be used by applications. [ 115.101088] umip: sidt[2578] ip:55a8f9ecf083 sp:7ffcd9824480: For now, expensive software emulation returns the result. [ 117.020143] umip: sidt[2580] ip:560d91114083 sp:7fff5851a7e0: SIDT instruction cannot be used by applications. [ 117.021026] umip: sidt[2580] ip:560d91114083 sp:7fff5851a7e0: For now, expensive software emulation returns the result. [ 117.532120] umip: sidt[2582] ip:55791bacf083 sp:7ffcab72a7b0: SIDT instruction cannot be used by applications. [ 235.100938] umip_printk: 252529 callbacks suppressed [ 235.100940] umip: sidt[31772] ip:557e4bdd1083 sp:7ffd62327520: SIDT instruction cannot be used by applications. [ 235.102641] umip: sidt[31772] ip:557e4bdd1083 sp:7ffd62327520: For now, expensive software emulation returns the result. [ 235.104214] umip: sidt[31773] ip:55b4f9a39083 sp:7fffe26616b0: SIDT instruction cannot be used by applications. [ 235.105075] umip: sidt[31773] ip:55b4f9a39083 sp:7fffe26616b0: For now, expensive software emulation returns the result. [ 235.106700] umip: sidt[31774] ip:555eff064083 sp:7ffec0fa7890: SIDT instruction cannot be used by applications. [ 355.104933] umip_printk: 397903 callbacks suppressed [ 355.104935] umip: sidt[4081] ip:55a1e12ea083 sp:7ffd1c9e9db0: SIDT instruction cannot be used by applications. [ 355.106654] umip: sidt[4081] ip:55a1e12ea083 sp:7ffd1c9e9db0: For now, expensive software emulation returns the result. [ 355.108232] umip: sidt[4082] ip:5572e28ae083 sp:7ffd515477f0: SIDT instruction cannot be used by applications. [ 355.109120] umip: sidt[4082] ip:5572e28ae083 sp:7ffd515477f0: For now, expensive software emulation returns the result. [ 355.110728] umip: sidt[4083] ip:55bfbcb64083 sp:7ffd16a2d350: SIDT instruction cannot be used by applications. [ 475.108935] umip_printk: 397107 callbacks suppressed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189773] Keyboard / Mouse do not work when connected through MT VIKI Auto USB KVM Switch
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189773 https://bugzilla.suse.com/show_bug.cgi?id=1189773#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Thomas Vatter from comment #16) > (In reply to Takashi Iwai from comment #15) > > If you switch back again from the graphics desktop to the text mode (e.g. > > plug another or re-plug the keyboard directly to the USB d or re-plug the > > same one to the USB port directly (without KVM), does it start working? > > > > The dmesg shows that the device have been recognized, at least. > > No, it doesn't. Hm, then you need to clarify which dmesg lines belong to which timing. I interpreted the lines about logitech things as the hotplugged events with KVM, but maybe it wasn't. That is, please identify whether the USB hotplug events get triggered by re-plugging to KVM. e.g. run "dmesg -w" on a terminal, then unplug the keyboard, and re-plug over the KVM. Which events are logged at which timing? -- You are receiving this mail because: You are the assignee for the bug.

1 0