Hi all,
I may found a potential bug when using qcom arm64 ramdump to parse backtrace.
Unfortunately, I actually found no processes can use the bt command correctly.
Ex: when start crash tool to do analyse: # crash vmlinux --kaslr=xxx
DDRCS0_0.BIN@0x8000,... --machdep vabits_actual=39
thanks Tao Liu！
--
Crash-utility mailing list -- devel@lists.crash-utility.osci.io
To unsubscribe send an email to devel-le...@lists.crash-utility.osci.io
https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
Contribution Guidelines: https://github.com/crash-utility/crash/wiki
From dd6b187ac15a237cefe863c4e5b432cf13b9883a Mon Sep 17 00:00:00 2001
From: bevis_chen
Date: Wed, 3 Jul 2024 15:05:44 +0800
Subject: [PATCH] arm64: Fix bt command show wrong stacktrace on ramdump source
If we use crash to parse ramdump(Qcom phone device) rathen than vmcore.
Start command should
Hi Tao Liu
patch has already fixed above.
thanks for your advice.
--
Crash-utility mailing list -- devel@lists.crash-utility.osci.io
To unsubscribe send an email to devel-le...@lists.crash-utility.osci.io
https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
Contribution Guidelines
Hi Lianbo
I have already added the origin commit information to patch log, as V3 below.
About the macro __GENMASK and GENMASK_UL.
Both the two macros achieve the same effect, but __GENMASK uses more addition
and subtraction operations and is usually called in an internal kernel core bi
fprintf(fp,
"CONFIG_ARM64_KERNELPACMASK: %lx\n",
+
machdep->machspec->CONFIG_ARM64_KERNELPACMASK);
+ }
+ }
+ }
+}
+
#endif /* ARM64 */
--
2.27.0
At 2024-07-15 11:33:13, "cb126yx" wrote:
Hi Lianbo
er suggestion, please feel free to let me know.
At 2024-07-16 19:20:33, "Tao Liu" wrote:
>Hi Lijiang,
>
>Thanks for the info.
>
>On Tue, Jul 16, 2024 at 9:51 PM lijiang wrote:
>>
>> Thank you for the update.
>>
>> On Mon, Jul 15, 2024 at 11:59 AM cb12
If we use crash tool to parse ramdump(Qcom phone device) rather than vmcore.
Start command should be like: crash vmlinux --kaslr=xxx
DDRCS0_0.BIN@0x8000,... --machdep vabits_actual=39
Then We will see bt command show misleading backtrace information as:
crash> bt 16930
PID: 1693
If we use crash to parse ramdump(Qcom phone device) rather than vmcore.
Start command should be like: crash vmlinux --kaslr=xxx
DDRCS0_0.BIN@0x8000,... --machdep vabits_actual=39
Then We will see bt command show misleading backtrace information as:
crash> bt 16930
PID: 16930TASK:
