Comments (10)
commented on September 28, 2024
----- Original Message -----
when trying to get stack frame with the command such as "bt -f" then, I could
see a warning message like below
"cannot determine starting stack frame for task".
What kind of dumpfile is it? What architecture?
and still could not get the correct callstack with its registers even though
message was just a warning.
What do you mean by "with its registers"?
from crash.
kasks80
commented on September 28, 2024
What kind of dumpfile is it? What architecture?
-> arch is arm64.(current I'm developing the android project)
-> how can i check kind of dumpfile?
I was confused. I mean when using "bt -t" or "bt -a", I could see below things.
PID: 16645 TASK: ffffffc027fa9180 CPU: 0 COMMAND: "Binder:16621_1"
bt: WARNING: cannot determine starting stack frame for task ffffffc027fa9180
actually I expected like the below result.(copy example from "help bt")
crash> bt -a
PID: 286 TASK: c0b3a000 CPU: 0 COMMAND: "in.rlogind"
#0 [c0b3be90] crash_save_current_state at c011aed0
#1 [c0b3bea4] panic at c011367c
#2 [c0b3bee8] tulip_interrupt at c01bc820
#3 [c0b3bf08] handle_IRQ_event at c010a551
#4 [c0b3bf2c] do_8259A_IRQ at c010a319
#5 [c0b3bf3c] do_IRQ at c010a653
#6 [c0b3bfbc] ret_from_intr at c0109634
EAX: 00000000 EBX: c0e68280 ECX: 00000000 EDX: 00000004 EBP: c0b3bfbc
DS: 0018 ESI: 00000004 ES: 0018 EDI: c0e68284
CS: 0010 EIP: c012f803 ERR: ffffff09 EFLAGS: 00000246
#7 [c0b3bfbc] sys_select at c012f803
#8 [c0b3bfc0] system_call at c0109598
EAX: 0000008e EBX: 00000004 ECX: bfffc9a0 EDX: 00000000
DS: 002b ESI: bfffc8a0 ES: 002b EDI: 00000000
SS: 002b ESP: bfffc82c EBP: bfffd224
CS: 0023 EIP: 400d032e ERR: 0000008e EFLAGS: 00000246
from crash.
commented on September 28, 2024
----- Original Message -----
What kind of dumpfile is it? What architecture?
-> arch is arm64.(current I'm developing the android project)
-> how can i check kind of dumpfile?
What is the output of "help -D"?
I'm confused. when using "bt -t" or "bt -a", i could see below things.
PID: 16645 TASK: ffffffc027fa9180 CPU: 0 COMMAND: "Binder:16621_1"
bt: WARNING: cannot determine starting stack frame for task ffffffc027fa9180
actually I expected like the below result.(copy example from "help bt")
crash> bt -a
PID: 286 TASK: c0b3a000 CPU: 0 COMMAND: "in.rlogind"
#0 [c0b3be90] crash_save_current_state at c011aed0
#1 [c0b3bea4] panic at c011367c
#2 [c0b3bee8] tulip_interrupt at c01bc820
#3 [c0b3bf08] handle_IRQ_event at c010a551
#4 [c0b3bf2c] do_8259A_IRQ at c010a319
#5 [c0b3bf3c] do_IRQ at c010a653
#6 [c0b3bfbc] ret_from_intr at c0109634
EAX: 00000000 EBX: c0e68280 ECX: 00000000 EDX: 00000004 EBP:
c0b3bfbc
DS: 0018 ESI: 00000004 ES: 0018 EDI: c0e68284
CS: 0010 EIP: c012f803 ERR: ffffff09 EFLAGS: 00000246
#7 [c0b3bfbc] sys_select at c012f803
#8 [c0b3bfc0] system_call at c0109598
EAX: 0000008e EBX: 00000004 ECX: bfffc9a0 EDX: 00000000
DS: 002b ESI: bfffc8a0 ES: 002b EDI: 00000000
SS: 002b ESP: bfffc82c EBP: bfffd224
CS: 0023 EIP: 400d032e ERR: 0000008e EFLAGS: 00000246
--
The WARNING message comes from here in arm64.c, where it is trying
to determine the starting pc and sp register values:
static void
arm64_get_stack_frame(struct bt_info *bt, ulong *pcp, ulong *spp)
{
int ret;
struct arm64_stackframe stackframe = { 0 };
if (DUMPFILE() && is_task_active(bt->task))
ret = arm64_get_dumpfile_stackframe(bt, &stackframe);
else
ret = arm64_get_stackframe(bt, &stackframe);
if (!ret)
error(WARNING,
"cannot determine starting stack frame for task %lx\n",
bt->task);
bt->frameptr = stackframe.fp;
if (pcp)
*pcp = stackframe.pc;
if (spp)
*spp = stackframe.sp;
}
Depending upon whether the "Binder:16621_1" task was active at the time
of the crash, it failed either in arm64_get_dumpfile_stackframe() or
arm64_get_stackframe(). If it was active, I'm presuming that it failed
at the top of arm64_get_dumpfile_stackframe():
static int
arm64_get_dumpfile_stackframe(struct bt_info *bt, struct arm64_stackframe *frame)
{
struct machine_specific *ms = machdep->machspec;
struct arm64_pt_regs *ptregs;
if (!ms->panic_task_regs ||
(!ms->panic_task_regs[bt->tc->processor].sp &&
!ms->panic_task_regs[bt->tc->processor].pc)) {
bt->flags |= BT_REGS_NOT_FOUND;
return FALSE;
}
...
You can determine whether the ms->panic_task_regs were set appropriately
like this:
crash> help -m
... [ cut ] ...
panic_task_regs: 39f3410
...
If it is non-zero (a user-space address), then perhaps the .sp or .pc
values for cpu 0 are NULL. Those values get set during initialization by the
arm_get_crash_notes() function. You could debug that function to see
whether they are getting set. It looks like there would have been some
type of warning message during initialization if it failed, but you didn't
send the output of the command.
Dave
from crash.
8yanghao
commented on September 28, 2024
I also meet such problem. on ARM64 platform I also can't restore the task bt;
crash> help -m
... [ cut ] ...
panic_task_regs: 0
...
but actually I get restore the pc, sp ptr from kmsg print or other way, is there any way to set the x0~x31 and PC, SP ptr by hand? and then the bt can work fine?
from crash.
commented on September 28, 2024
----- Original Message -----
I also meet such problem. on ARM64 platform I also can't restore the task bt;
crash> help -m
... [ cut ] ...
panic_task_regs: 0
...
but actually I get restore the pc, sp ptr from kmsg print or other way, is
there any way to set the x0~x31 and PC, SP ptr by hand? and then the bt can
work fine?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#22 (comment)
You can try using the bt command's "-I <instruction-address> -S <stack-address>"
options and try to make it work. The two options are designed for the x86_86
architecture, but it's worth a try. For example, take the pc and sp arguments
from the log:
[ 744.483512] pc : machine_kexec+0x58/0x3e8
[ 744.531499] lr : machine_kexec+0x58/0x3e8
[ 744.579486] sp : ffff000011b4f6a0
and then try "bt -I machine_kexec+0x58" -S ffff000011b4f6a0". If that doesn't
work, try adding or subtracting 8 from the stack address.
Dave
from crash.
slowpy
commented on September 28, 2024
in arm64,the crash tool check pstate
from crash.
taigerhu
commented on September 28, 2024
I also meet such problem. on ARM64 platform I also can't restore the task bt;
crash> help -m
... [ cut ] ...
panic_task_regs: 0
...
but actually I get restore the pc, sp ptr from kmsg print or other way, is there any way to set the x0~x31 and PC, SP ptr by hand? and then the bt can work fine?
hi
i already debug the function, seems no crash_notes symbol, did you side fix the issue?
Thx.
from crash.
praton1729
commented on September 28, 2024
Hi guys,
I was able to get the bt(still with one error message) by adding/subtracting(yes, both worked) 8 from sp on arm64. The printed register values are not correct though.
P.S: help -D and help -m output is attached.
help_D.txt
help_m.txt
from crash.
YuanyeMa
commented on September 28, 2024
Hi guys,
I also meet such problem. on ARM64 platform.
Adding/subtracting 8 from sp is does not work yet.
Corefile type : vmcore_data
panic_task_regs: 0
crash> bt 1
PID: 1 TASK: ffffff95c514bd40 CPU: 7 COMMAND: "init"
bt: WARNING: cannot determine starting stack frame for task ffffff95c514bd40
crash> bt -I 0x00000558f52a1a4 -S 0x000007fca225500 1
PID: 1 TASK: ffffff95c514bd40 CPU: 7 COMMAND: "init"
bt: non-process stack address for this task: 7fca225500
(valid range: ffffffc010060000 - ffffffc010064000)
crash> bt -I 0x00000558f52a1a4 -S 0x000007fca225508 1
PID: 1 TASK: ffffff95c514bd40 CPU: 7 COMMAND: "init"
bt: non-process stack address for this task: 7fca225508
(valid range: ffffffc010060000 - ffffffc010064000)
Does anyone have any ideas to solve this problem?
Thanks Very Much
from crash.
YuanyeMa
commented on September 28, 2024
When the crash is just started, the following print is displayed. Does it matter?
WARNING: cpu 0: cannot find NT_PRSTATUS note
WARNING: cpu 1: cannot find NT_PRSTATUS note
WARNING: cpu 2: cannot find NT_PRSTATUS note
WARNING: cpu 3: cannot find NT_PRSTATUS note
WARNING: cpu 4: cannot find NT_PRSTATUS note
WARNING: cpu 5: cannot find NT_PRSTATUS note
WARNING: cpu 6: cannot find NT_PRSTATUS note
WARNING: cpu 7: cannot find NT_PRSTATUS note
Also, is the issue related to zram enabled in the kernel?
Thanks.
from crash.
Related Issues (20)
- Swapped page read failure in Linux v6.1-rc4
- WARNING: invalid linux_banner pointer: 65762078756e694c + vmlinux and /proc/kcore do not match! HOT 7
- Compilation error when doing cross compilation for arm64 HOT 7
- kaslr error
- crash utility: add log / dmesg PRINTK_CALLER id support HOT 5
- I cannot run gdb command in crash HOT 1
- Is there any way I can set the registers manually?
- Can not load arm64 dumpfile HOT 2
- bt command coredump HOT 2
- Use .orc_header to detect version
- crash: invalid kernel virtual address: 0 type: "module symbols"
- How do I get a list of open network sockets for kernel threads?
- Segmentation fault seen while decoding ARM64 kdump. HOT 5
- [ARM] Crash failed to parse the core header when makedumpfile is compiled with -D_TIME_BITS=64 HOT 5
- [ARM] Is there any plan to add support for kaslr on arm platform. HOT 1
- Unable to load compressed module *.ko.zst file using mod command
- x86: WARNING: could not find MAGIC_START!
- bt command issue and don't know how to handle section `. relr. dyn' [0x13]
- Could you please upgrade the gdb version to the newest? HOT 2
- How to support for android15-linux6.6 gki crash tools ? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from crash.