From: jgq516@gmail.com (jgq516 at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: ftrace calltrace when boot through kexec
Date: Wed, 29 May 2013 13:25:14 +0800 [thread overview]
Message-ID: <51A5913A.5030302@gmail.com> (raw)
Hello,
When I reboot a preempt_rt 3.4 kernel with cortex a15 tc2 board thru
kexec, I got below calltrace appeared:
------------[ cut here ]------------
WARNING: at kernel/trace/ftrace.c:1584 ftrace_bug+0x1e0/0x224()
Modules linked in:
[<c0017e14>] (unwind_backtrace+0x0/0x104) from [<c062a468>]
(dump_stack+0x20/0x24)
[<c062a468>] (dump_stack+0x20/0x24) from [<c00265a4>]
(warn_slowpath_common+0x64/0x74)
[<c00265a4>] (warn_slowpath_common+0x64/0x74) from [<c00265e0>]
(warn_slowpath_null+0x2c/0x34)
[<c00265e0>] (warn_slowpath_null+0x2c/0x34) from [<c00bf70c>]
(ftrace_bug+0x1e0/0x224)
[<c00bf70c>] (ftrace_bug+0x1e0/0x224) from [<c00c03b4>]
(ftrace_process_locs+0x880/0x930)
[<c00c03b4>] (ftrace_process_locs+0x880/0x930) from [<c082d018>]
(ftrace_init+0xb4/0x194)
[<c082d018>] (ftrace_init+0xb4/0x194) from [<c081e8c4>]
(start_kernel+0x338/0x348)
[<c081e8c4>] (start_kernel+0x338/0x348) from [<80008054>] (0x80008054)
---[ end trace af5b256dd27bb7ab ]---
ftrace failed to modify [<c0022b88>] platform_cpu_kill+0x10/0x1c
actual: 00:40:bd:e8
Add notrace before platform_cpu_kill can workaround this calltrace, but
it is weird that this problem can't
reproduce in another cortex-a9 (xilinx-zynq) board, could someone give
some hints about this? Thanks.
Regards,
Xiao
WARNING: multiple messages have this Message-ID (diff)
From: jgq516@gmail.com
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: ftrace calltrace when boot through kexec
Date: Wed, 29 May 2013 13:25:14 +0800 [thread overview]
Message-ID: <51A5913A.5030302@gmail.com> (raw)
Hello,
When I reboot a preempt_rt 3.4 kernel with cortex a15 tc2 board thru
kexec, I got below calltrace appeared:
------------[ cut here ]------------
WARNING: at kernel/trace/ftrace.c:1584 ftrace_bug+0x1e0/0x224()
Modules linked in:
[<c0017e14>] (unwind_backtrace+0x0/0x104) from [<c062a468>]
(dump_stack+0x20/0x24)
[<c062a468>] (dump_stack+0x20/0x24) from [<c00265a4>]
(warn_slowpath_common+0x64/0x74)
[<c00265a4>] (warn_slowpath_common+0x64/0x74) from [<c00265e0>]
(warn_slowpath_null+0x2c/0x34)
[<c00265e0>] (warn_slowpath_null+0x2c/0x34) from [<c00bf70c>]
(ftrace_bug+0x1e0/0x224)
[<c00bf70c>] (ftrace_bug+0x1e0/0x224) from [<c00c03b4>]
(ftrace_process_locs+0x880/0x930)
[<c00c03b4>] (ftrace_process_locs+0x880/0x930) from [<c082d018>]
(ftrace_init+0xb4/0x194)
[<c082d018>] (ftrace_init+0xb4/0x194) from [<c081e8c4>]
(start_kernel+0x338/0x348)
[<c081e8c4>] (start_kernel+0x338/0x348) from [<80008054>] (0x80008054)
---[ end trace af5b256dd27bb7ab ]---
ftrace failed to modify [<c0022b88>] platform_cpu_kill+0x10/0x1c
actual: 00:40:bd:e8
Add notrace before platform_cpu_kill can workaround this calltrace, but
it is weird that this problem can't
reproduce in another cortex-a9 (xilinx-zynq) board, could someone give
some hints about this? Thanks.
Regards,
Xiao
next reply other threads:[~2013-05-29 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 5:25 jgq516 at gmail.com [this message]
2013-05-29 5:25 ` ftrace calltrace when boot through kexec jgq516
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=51A5913A.5030302@gmail.com \
--to=jgq516@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.