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@opensuse.org Reporter: giovanni.gherdovich@suse.com QA Contact: qa-bugs@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.