January 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1181111] New: Dynamic Debugging (dyndbg) query at boot fails on module acpi_cpufreq
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181111 Bug ID: 1181111 Summary: Dynamic Debugging (dyndbg) query at boot fails on module acpi_cpufreq 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: giovanni.gherdovich(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 845262 --> http://bugzilla.opensuse.org/attachment.cgi?id=845262&action=edit "acpi_cpufreq.dyndbg= file drivers/cpufreq/acpi-cpufreq.c +mpf" (dmesg | grep dyndbg) The following dyndbg query, added to the kernel command line (kernel version v5.11-rc3) doesn't produce the expected debugging logs: "acpi_cpufreq.dyndbg= file drivers/cpufreq/acpi-cpufreq.c +mpf" The following output shows that the query is partially understood, but it's been noted that it should not say "acpi_cpufreq_exit =_", but rather "acpi_cpufreq_exit =mpf" # cat /sys/kernel/debug/dynamic_debug/control | grep acpi-cpufreq drivers/cpufreq/acpi-cpufreq.c:980 [acpi_cpufreq]acpi_cpufreq_exit =_ "%s\012" drivers/cpufreq/acpi-cpufreq.c:959 [acpi_cpufreq]acpi_cpufreq_init =_ "CPB unsupported, do not expose it\012" drivers/cpufreq/acpi-cpufreq.c:943 [acpi_cpufreq]acpi_cpufreq_init =_ "%s\012" drivers/cpufreq/acpi-cpufreq.c:906 [acpi_cpufreq]acpi_cpufreq_boost_init =_ "Boost capabilities not present in the processor\012" drivers/cpufreq/acpi-cpufreq.c:870 [acpi_cpufreq]acpi_cpufreq_resume =_ "%s\012" drivers/cpufreq/acpi-cpufreq.c:845 [acpi_cpufreq]acpi_cpufreq_cpu_exit =_ "%s\012" drivers/cpufreq/acpi-cpufreq.c:817 [acpi_cpufreq]acpi_cpufreq_cpu_init =_ " %cP%d: %d MHz, %d mW, %d uS\012" drivers/cpufreq/acpi-cpufreq.c:811 [acpi_cpufreq]acpi_cpufreq_cpu_init =_ "CPU%u - ACPI performance management activated.\012" drivers/cpufreq/acpi-cpufreq.c:748 [acpi_cpufreq]acpi_cpufreq_cpu_init =_ "Unknown addr space %d\012" drivers/cpufreq/acpi-cpufreq.c:731 [acpi_cpufreq]acpi_cpufreq_cpu_init =_ "HARDWARE addr space\012" drivers/cpufreq/acpi-cpufreq.c:725 [acpi_cpufreq]acpi_cpufreq_cpu_init =_ "SYSTEM IO addr space\012" drivers/cpufreq/acpi-cpufreq.c:721 [acpi_cpufreq]acpi_cpufreq_cpu_init =_ "AMD K8 systems must use native drivers.\012" drivers/cpufreq/acpi-cpufreq.c:707 [acpi_cpufreq]acpi_cpufreq_cpu_init =_ "No P-States\012" drivers/cpufreq/acpi-cpufreq.c:645 [acpi_cpufreq]acpi_cpufreq_cpu_init =_ "%s\012" drivers/cpufreq/acpi-cpufreq.c:565 [acpi_cpufreq]acpi_cpufreq_early_init =_ "Memory allocation error for acpi_perf_data.\012" drivers/cpufreq/acpi-cpufreq.c:561 [acpi_cpufreq]acpi_cpufreq_early_init =_ "%s\012" drivers/cpufreq/acpi-cpufreq.c:447 [acpi_cpufreq]acpi_cpufreq_target =_ "%s (%d)\012" drivers/cpufreq/acpi-cpufreq.c:430 [acpi_cpufreq]acpi_cpufreq_target =_ "Already at target state (P%d)\012" drivers/cpufreq/acpi-cpufreq.c:426 [acpi_cpufreq]acpi_cpufreq_target =_ "Called after resume, resetting to P%d\012" drivers/cpufreq/acpi-cpufreq.c:387 [acpi_cpufreq]get_cur_freq_on_cpu =_ "cur freq = %u\012" drivers/cpufreq/acpi-cpufreq.c:367 [acpi_cpufreq]get_cur_freq_on_cpu =_ "%s (%d)\012" drivers/cpufreq/acpi-cpufreq.c:355 [acpi_cpufreq]get_cur_val =_ "%s = %u\012" drivers/cpufreq/acpi-cpufreq.c:134 [acpi_cpufreq]set_boost =_ "CPU %*pbl: Core Boosting %sabled.\012" A snippet of the boot log using dynamic_debug.verbose=2 is attached. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1181104] Unplugging TeVII DVB-S2 USB adapter crashes kernel
by bugzilla_noreply＠suse.com 19 Jan '21

19 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1181104 https://bugzilla.suse.com/show_bug.cgi?id=1181104#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 Oops itself looks like the NULL dereference at dvb_usb_device_exit(), and it's the part: if (d != NULL && d->desc != NULL) { strscpy(name, d->desc->name, sizeof(name)); So adding the NULL check of d->desc->name should paper over it, e.g. if (d != NULL && d->desc != NULL && d->desc->name != NULL) { strscpy(name, d->desc->name, sizeof(name)); (It's better to rewrite the if condition without "!= NULL", though.) However, this doesn't explain why d->desc->name can be NULL. My wild guess is that this is use-after-free, the properties object got already released at disconnection, but this needs to be checked by the upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180711] External monitor DEAD after logging in - works in console / SDDM since updating to 20210106
by bugzilla_noreply＠suse.com 18 Jan '21

18 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180711 https://bugzilla.suse.com/show_bug.cgi?id=1180711#c9 --- Comment #9 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- Let's close it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1181026] New: Cannot boot any kernel version starting from 5.10...
by bugzilla_noreply＠suse.com 18 Jan '21

18 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181026 Bug ID: 1181026 Summary: Cannot boot any kernel version starting from 5.10... 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: hehe_br-opensuse(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 845210 --> http://bugzilla.opensuse.org/attachment.cgi?id=845210&action=edit lspci I cannot boot any kernel version starting from 5.10... Problem started with the kernel update from Tumbleweed 20201223. All later updates are of no help. System does not boot with the workaround suggested https://bugzilla.opensuse.org/show_bug.cgi?id=1180344. It also does not leave log messages in journalctl even in recovery mode. Running fine with: Linux version 5.9.10-1-default (geeko@buildhost) (gcc (SUSE Linux) 10.2.1 20201117 [revision 98ba03ffe0b9f37b4916ce6238fad754e00d720b], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.35.1.20201112-1) #1 SMP Mon Nov 23 09:08:45 UTC 2020 (b7c3768) BOOT_IMAGE=/boot/vmlinuz-5.9.10-1-default root=UUID=n resume=/dev/disk/by-uuid/n splash=silent quiet showopts amdgpu.si_support=1 radeon.si_support=0 acpi_backlight=amdgpu_bl0 tumbleweed installed: 20210107 kernel-default-5.10.4-1.1.x86_64 kernel-default-5.10.3-1.2.x86_64 kernel-default-5.9.10-1.1.x86_64 ASUS X550IU, BIOS X550IU.308 04/19/2019 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1180742] [amdgpu]An AMD Vega series GPU randomly crashes
by bugzilla_noreply＠suse.com 18 Jan '21

18 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180742 https://bugzilla.suse.com/show_bug.cgi?id=1180742#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Iakov Karpov from comment #2) > (In reply to Takashi Iwai from comment #1) > > It's some GPU hang that leads to the real kernel crash.... which happened on > > others sometimes, too. Unfortunately there is no fix for this and likely > > not for Leap 15.2 kernel. > > > > Could you try the kernel in OBS Kernel:stable or SLE15-SP3 kernel in OBS > > Kernel:SLE15-SP3? The latter contains the backport of DRM stack up to 5.9.x. > > kernel 5.3.18-100.g3524980 of Kernel:SLES15-SP3 won't boot on this machine > (stuck right after bootloader, not even a single line after "loading initrd" > on screen. That's bad. Do you have the secure boot enabled? If so, disable it when you test a kernel from OBS repo that is other than the official release. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180711] External monitor DEAD after logging in - works in console / SDDM since updating to 20210106
by bugzilla_noreply＠suse.com 18 Jan '21

18 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180711 https://bugzilla.suse.com/show_bug.cgi?id=1180711#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- So, does everything work now as expected? Or do you see any issues to be fixed now? If not, let's close the bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180591] Display backlight stuck at 100%
by bugzilla_noreply＠suse.com 18 Jan '21

18 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180591 https://bugzilla.suse.com/show_bug.cgi?id=1180591#c15 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(maurizio.galli@gm | |ail.com) | --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. I checked briefly between v5.7 and v5.8, but there is no change in either driver/acpi/video_detect.c or drivers/acpi/acpi_video.c. So the ACPI code (in those areas) didn't change, and something else (also in ACPI) must be the cause of the regression. It's hard to tell for now. And, I looked at the backlight support on Apple machines and they are... well... messy. There is apple-gmux driver that supports things on some devices but it's only for ACPI APP000B, which isn't enabled on yours. At this moment, the best thing we can do is to git bisect. But of course it takes time (and patience). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180962] New: Kernel did not see the status numlock from bios.
by bugzilla_noreply＠suse.com 18 Jan '21

18 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180962 Bug ID: 1180962 Summary: Kernel did not see the status numlock from bios. 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: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel did not see the status numlock from bios. After several updates I found what the numlock status is off by default. Checking the setting in BIOS. It is on by default With settings KBD_NUMLOCK="bios" in /etc/sysconfig/keyboard it is always off. -- You are receiving this mail because: You are the assignee for the bug.

1 7

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

18 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kernel-bugs@opens | |use.org) | -- 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 18 Jan '21

18 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c14 --- Comment #14 from Michal Suchanek <msuchanek(a)suse.com> --- cherry-picked the arm64 patches from upstream here https://build.opensuse.org/request/show/864052 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0