Hi Dave, I gave a talk at SCaLE 17x last week and was going to demonstrate using ftrace on a system that crashes, and then pulling out the vmcore file with kexec and kdump, and then pulling out the ftrace ring buffers and creating a trace.dat file with the crash extension trace.so. Unfortunately, this wasn't working as I planned. I created the following three patches, where two fix the issue (I was getting a corrupted trace.dat file), and the third actually documents the '-t' option of the dump command. Hopefully you can accept these patches. Thanks! -- Steve ----- extensions/trace.c | 32 +++++++++++++++++++++++++++++--- 1 file changed, 29 insertions(+), 3 deletions(-) Steven Rostedt (VMware) (3): trace.so: Do not record empty pages trace.so: Do not print garbage for kallsyms "type" for modules trace.so: Show -t option in trace dump short help message