From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: LTP-tracing: WARNING: at kernel/trace/trace_functions_graph.c:1005 print_graph_entry
Date: Thu, 22 May 2025 17:03:50 +0530 [thread overview]
Message-ID: <CA+G9fYvxyha0sgEsc8h9FGT2=NOtMq676KtmDCyBsb54X+axHA@mail.gmail.com> (raw)
Regressions while running LTP tracing on Linus tree master 6.15.0-rc7
on arm64 Dragonboard 845c and Dragonboard 410c the following kernel
warnings were noticed.
Also noticed intermittently from Linux next-20250410 till next-20250521
on the arm, arm64 and x86_64 devices.
Regressions found on Dragonboard 845c and Dragonboard 410c
- LTP tracing
Regression Analysis:
- New regression? Yes
- Reproducible? Intermittent
Test regression: Dragonboard 845c WARNING trace_functions_graph.c
print_graph_entry
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
## Test log (64k PAGE size boot and test log)
tee /lava-166778/0/tests/0_ltp-tracing/automated/linux/ltp/output/LTP_tracing.out
Host information
System: Linux
Node: runner-j1aldqxs-project-40964107-concurrent-0
Kernel Release: 6.15.0-rc7
Kernel Version: #1 SMP PREEMPT @1747826135
Machine Architecture: aarch64
Processor:
Temporary directory: /scratch/kirk.root/tmp6l2lrw3o
Connecting to SUT: host
Starting suite: shardfile
ftrace_regression01: pass (0.975s)
ftrace_regression02: [ 24.865534] /usr/local/bin/kirk[769]: starting
test ftrace_regression02 (ftrace_regression02.sh)
pass (1.037s)
ftrace-stress-test: [ 25.946741] /usr/local/bin/kirk[769]: starting
test ftrace-stress-test (ftrace_stress_test.sh 90)
[ 35.063437] Scheduler tracepoints stat_sleep, stat_iowait,
stat_blocked and stat_runtime require the kernel parameter
schedstats=enable or kernel.sched_schedstats=1
[ 35.063795] Scheduler tracepoints stat_sleep, stat_iowait,
stat_blocked and stat_runtime require the kernel parameter
schedstats=enable or kernel.sched_schedstats=1
[ 97.866749] ------------[ cut here ]------------
[ 97.871613] WARNING: CPU: 6 PID: 13314 at
kernel/trace/trace_functions_graph.c:1005 print_graph_entry
(kernel/trace/trace_functions_graph.c:1005 (discriminator 1)
kernel/trace/trace_functions_graph.c:1229 (discriminator 1))
[ 97.882169] Modules linked in: snd_soc_hdmi_codec ax88179_178a
usbnet fuse ip_tables x_tables venus_enc venus_dec mcp251xfd
videobuf2_dma_contig snd_soc_sdm845 xhci_pci_renesas can_dev
lontium_lt9611 msm snd_soc_rt5663 leds_qcom_lpg ath10k_snoc
snd_soc_qcom_sdw hci_uart rtc_pm8xxx ocmem qcom_pbs btqca
snd_soc_qcom_common drm_exec ath10k_core qcom_spmi_adc5 btbcm
qcom_spmi_temp_alarm qcom_vadc_common ath led_class_multicolor
gpu_sched qcom_stats snd_soc_rl6231 mac80211 drm_dp_aux_bus
drm_display_helper qcom_pon drm_client_lib reset_qcom_pdc
soundwire_bus cfg80211 qcom_camss videobuf2_dma_sg bluetooth
videobuf2_memops venus_core phy_qcom_qmp_combo v4l2_mem2mem aux_bridge
coresight_stm videobuf2_v4l2 camcc_sdm845 pwrseq_core videobuf2_common
i2c_qcom_geni qcom_rng typec qcom_q6v5_mss phy_qcom_qmp_usb ufs_qcom
spi_geni_qcom phy_qcom_qmp_ufs qcrypto gpi qrtr rfkill stm_core
qcom_wdt phy_qcom_qmp_pcie lmh icc_osm_l3 slim_qcom_ngd_ctrl slimbus
pdr_interface qcom_pdr_msg qcom_q6v5_pas qcom_pil_info qcom_q6v5
qcom_sysmon
[ 97.884162] qcom_common icc_bwmon llcc_qcom qcom_glink_smem
mdt_loader display_connector drm_kms_helper qmi_helpers drm backlight
socinfo rmtfs_mem
[ 97.989673] CPU: 6 UID: 0 PID: 13314 Comm: cat Not tainted
6.15.0-rc7 #1 PREEMPT
[ 97.997392] Hardware name: Thundercomm Dragonboard 845c (DT)
[ 98.003243] pstate: a0400005 (NzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 98.010424] pc : print_graph_entry
(kernel/trace/trace_functions_graph.c:1005 (discriminator 1)
kernel/trace/trace_functions_graph.c:1229 (discriminator 1))
[ 98.015043] lr : print_graph_entry
(kernel/trace/trace_functions_graph.c:604
kernel/trace/trace_functions_graph.c:1225)
[ 98.019659] sp : ffff80008fd8fb10
[ 98.023126] x29: ffff80008fd8fb70 x28: ffff124e013d5700 x27: ffff124e013d5720
[ 98.030552] x26: ffffdb1ef470098c x25: 0000000000000001 x24: ffff124e013d5700
[ 98.037984] x23: ffff124e18cac000 x22: 0000000000000696 x21: 00000000fefefefe
[ 98.045410] x20: ffff124e18ca8000 x19: ffff124e18caa090 x18: 0000000000000000
[ 98.052835] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[ 98.060265] x14: 0000000000000001 x13: 0000000000000001 x12: 000003dd0200000b
[ 98.067696] x11: ffffdb1ef713c5f0 x10: 0000000000000020 x9 : ffffdb1ef462ac10
[ 98.075126] x8 : 0000000000000020 x7 : 0000000000000001 x6 : 0000000000000029
[ 98.082552] x5 : ffff124e18caa094 x4 : ffffdb1ef6754af6 x3 : 0000000000000001
[ 98.089979] x2 : ffffdb1ef713b208 x1 : ffff372f84970000 x0 : ffffffdfbf6bd8e0
[ 98.097407] Call trace:
[ 98.099979] print_graph_entry
(kernel/trace/trace_functions_graph.c:1005 (discriminator 1)
kernel/trace/trace_functions_graph.c:1229 (discriminator 1)) (P)
[ 98.104598] print_graph_function_flags
(kernel/trace/trace_functions_graph.c:1423)
[ 98.109654] print_graph_function (kernel/trace/trace_functions_graph.c:1467)
[ 98.114005] print_trace_line (kernel/trace/trace.c:4347)
[ 98.118091] tracing_read_pipe (kernel/trace/trace.c:3840
kernel/trace/trace.c:6686)
[ 98.122358] vfs_read (fs/read_write.c:568)
[ 98.125734] ksys_read (fs/read_write.c:713) (F)
[ 98.129555] __arm64_sys_read (fs/read_write.c:720) (F)
[ 98.133903] invoke_syscall.constprop.0
(arch/arm64/include/asm/syscall.h:61 arch/arm64/kernel/syscall.c:54)
(F)
[ 98.139146] do_el0_svc (arch/arm64/kernel/syscall.c:139
arch/arm64/kernel/syscall.c:151) (F)
[ 98.142968] el0_svc (arch/arm64/include/asm/irqflags.h:82
(discriminator 1) arch/arm64/include/asm/irqflags.h:123 (discriminator
1) arch/arm64/include/asm/irqflags.h:136 (discriminator 1)
arch/arm64/kernel/entry-common.c:165 (discriminator 1)
arch/arm64/kernel/entry-common.c:178 (discriminator 1)
arch/arm64/kernel/entry-common.c:745 (discriminator 1)) (F)
[ 98.146615] el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:763)
[ 98.151144] el0t_64_sync (arch/arm64/kernel/entry.S:600)
[ 98.154966] ---[ end trace 0000000000000000 ]---
Restarting SUT: host
dynamic_debug01: [ 123.083214] /usr/local/bin/kirk[769]: starting
test dynamic_debug01 (dynamic_debug01.sh)
## Source
* Kernel version: 6.15.0-rc7
* Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git
* Git sha: 4a95bc121ccdaee04c4d72f84dbfa6b880a514b6
## Build
* Test log: https://lkft-staging.validation.linaro.org/scheduler/job/166778#L6126
* Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/2xP3N7qYnNfT17IiSMUStDcHHHG/
* Kernel config:
https://storage.tuxsuite.com/public/linaro/lkft/builds/2xP3N7qYnNfT17IiSMUStDcHHHG/config
--
Linaro LKFT
https://lkft.linaro.org
reply other threads:[~2025-05-22 11:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+G9fYvxyha0sgEsc8h9FGT2=NOtMq676KtmDCyBsb54X+axHA@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mhiramat@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).