Using crash to dump trace information
by Pete Delaney -T (petdelan - RANDSTAD NORTH AMERICA INC＠Cisco)
Hi Dave:
I compiled crash-utility to run on X86 and handle vmcore files for a 32bit arm.
I would like to use crash to dump the trace buffer, as described here:
https://access.redhat.com/solutions/239433
it relies on using a trace.so which is dependent on the kernel version.
$ crash --osrelease vmcore*
4.9.170
Since this is a homegrown version of 4.9 I suspect that I'd need to make the trace.so locally.
Is that something I can do without a lot of work?
-pete delaney
4 years, 9 months
- 2
- 1
[PATCH] Fix for the "log -a" option
by qiwuchen55＠gmail.com
From: chenqiwu <chenqiwu(a)xiaomi.com>
Fix for the "log -a" option. The printk logbuf is a ring buffer,
if log_first_idx is larger than log_next_idx, there are two buffer
zones must be handled for logdump:
1) [log_first_idx, log_buf_len]
2) [0, log_next_idx]
However, the original code ignores the logdump for the second buffer
zone if log_first_idx is larger than log_next_idx. Without this patch,
the option fails with the following error message "duplicate log_buf
message pointer".
Signed-off-by: chenqiwu <chenqiwu(a)xiaomi.com>
---
kernel.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/kernel.c b/kernel.c
index 68ee282..7604fac 100644
--- a/kernel.c
+++ b/kernel.c
@@ -5278,8 +5278,12 @@ dump_variable_length_record_log(int msg_flags)
idx = log_next(idx, logbuf);
if (idx >= log_buf_len) {
- error(INFO, "\ninvalid log_buf entry encountered\n");
- break;
+ if (log_first_idx > log_next_idx)
+ idx = 0;
+ else {
+ error(INFO, "\ninvalid log_buf entry encountered\n");
+ break;
+ }
}
if (CRASHDEBUG(1) && (idx == log_next_idx))
--
1.9.1
4 years, 9 months
- 3
- 3
Support for crash running on an ARM 32 bit host analyzing ARM 32 bit crash files? Looking unlikely. :(
by Pete Delaney -T (petdelan - RANDSTAD NORTH AMERICA INC＠Cisco)
Hi Dave:
I tried to build crash-utility to run on a 32 bit ARM to analyze 32 bit ARM crash dumps.
On looking at the Make file it appeared that ARM is supported.
#
# Supported targets: X86 ALPHA PPC IA64 PPC64 SPARC64
# TARGET and GDB_CONF_FLAGS will be configured automatically by configure
#
I was a bit disappointed. ☹
Any hope (in the future perhaps)?
-piet
4 years, 9 months
- 3
- 5