01:51
hpt has joined #systemtap
02:04
orivej has joined #systemtap
04:32
irker164 has quit [Quit: transmission timeout]
06:01
slowfranklin has joined #systemtap
07:03
orivej has quit [Ping timeout: 240 seconds]
07:35
orivej has joined #systemtap
07:56
slowfranklin has quit [Quit: slowfranklin]
08:52
slowfranklin has joined #systemtap
09:25
mjw has joined #systemtap
09:34
hpt has quit [Ping timeout: 255 seconds]
09:54
gila has joined #systemtap
10:15
higgins has quit [Quit: Leaving]
10:21
higgins has joined #systemtap
12:39
slowfranklin has quit [Quit: slowfranklin]
12:42
slowfranklin has joined #systemtap
12:53
khaled has joined #systemtap
12:54
slowfranklin has quit [Quit: slowfranklin]
12:58
mjw has quit [Quit: Leaving]
13:27
slowfranklin has joined #systemtap
13:40
hpt has joined #systemtap
13:42
wcohen has quit [Ping timeout: 250 seconds]
14:14
hpt has quit [Ping timeout: 245 seconds]
14:39
sscox has joined #systemtap
14:42
wcohen has joined #systemtap
14:49
tromey has joined #systemtap
16:37
irker967 has joined #systemtap
16:37
<
irker967 >
systemtap: fche systemtap.git:refs/heads/master * release-4.0-124-g18d1bac / session.cxx: session.cxx diagnostics: don't dump kernel_functions below verbose=6
http://tinyurl.com/yxbepqun
16:39
<
fche >
wcohen, if you still happen to have access to an arm64 box
16:40
<
wcohen >
fche, yes I do.
16:40
<
fche >
would you be able to give a quick test to BZ1658163, to see what might be going on?
16:44
<
fche >
so -DDEBUG_UNWIND -DDEBUG_SYMS etc. kind of data gathering would be good
16:45
<
wcohen >
the arm64 box I have is running fedora 29 4.20.10 kernel and a git build of systemtap. the rhbzZ1658163 on this environment gives the same abbreviated backtrace.
16:45
<
fche >
ok, should be useful to get the similar info then
16:51
<
wcohen >
fche, added a comment with the run with --DEBUG_UNWIND -DDEBUG_SYMS to BZ1658163
16:52
<
wcohen >
fche, I vaguely remember some issues with backtraces aarch64 backtraces some years ago.
16:53
* wcohen
trying to look up discussion on that.
16:53
<
fche >
-DDEBUG_SYMBOLS rather than DEBUG_SYMS, and maybe -DDEBUG_TRANS please
16:54
<
fche >
basically we should see what kernel stext / module addresses are being sent to the stap module
16:55
slowfranklin has left #systemtap [#systemtap]
16:55
<
fche >
the eh_frame data alone should be fine (if slow), but it seems as though not even that was working here
16:56
dmalcolm has quit [Remote host closed the connection]
16:56
<
wcohen >
fche, yes, they may not be the same root cause.
17:05
<
wcohen >
fche, attached stap results as an attachment to the bz. anything look odd in the output?
17:06
<
wcohen >
want me to set some additional defines or flags for the run?
17:07
<
fche >
yes, -DDEBUG_SYMBOLS and -DDEBUG_TRANS please
17:08
dmalcolm has joined #systemtap
17:09
<
wcohen >
I attached the output to the wrong bz. take another look at 1658163, fche.
17:22
<
wcohen >
towards the end of stap_results.out it says:
17:22
<
wcohen >
unwind:1490: pc=ffff0000082de7e8, ffff0000082de7e8
17:22
<
wcohen >
unwind_frame:1190: Module /usr/lib/debug/usr/lib/modules/4.20.10-200.fc29.aarch64/vmlinux: no unwind frame data
17:22
<
wcohen >
unwind:1537: debug_frame failed: -5, trying eh_frame
17:22
<
wcohen >
unwind:1533: trying debug_frame
17:22
<
wcohen >
unwind_frame:1190: Module /usr/lib/debug/usr/lib/modules/4.20.10-200.fc29.aarch64/vmlinux: no unwind frame data
17:23
<
wcohen >
are the "no unwind frame data" expected?
17:25
<
wcohen >
I am wondering if there might be some kernel config change that caused aarch64 backtraces to stop working.
17:44
<
fche >
would look at the hex address from first principles
17:44
<
fche >
that 0xffff0000082de7e8 number should fit into one of the ranges used by the modules
17:46
<
fche >
or a sym within the kernel itself; does /proc/kallsyms contain addresses in that range?
17:47
slowfranklin has joined #systemtap
17:47
<
wcohen >
fche, that is definitely the start of the kmem_cache_alloc function in the kernel.
17:48
slowfranklin has quit [Client Quit]
17:49
<
wcohen >
fche, adding nokaslr to the kernel command line didn't make difference.
17:51
<
fche >
what does a stap -k .... stap-symbols.h look like w.r.t. the kernel eh-frame data? it should contain some relocation info
17:54
<
fche >
near the bottom of the file
17:58
<
wcohen >
there doesn't seem to be much eh_frame data.
18:11
slowfranklin has joined #systemtap
18:47
slowfranklin has quit [Quit: slowfranklin]
19:01
slowfranklin has joined #systemtap
19:02
slowfranklin has quit [Client Quit]
19:23
slowfranklin has joined #systemtap
19:29
vbernat has quit [Quit: The future belongs to those who believe in the beauty of their dreams.]
19:29
vbernat has joined #systemtap
19:37
irker967 has quit [Quit: transmission timeout]
20:40
slowfranklin has quit [Quit: slowfranklin]
20:51
slowfranklin has joined #systemtap
21:05
slowfranklin has quit [Quit: slowfranklin]
21:12
slowfranklin has joined #systemtap
21:34
orivej has quit [Ping timeout: 246 seconds]
21:59
tromey has quit [Ping timeout: 240 seconds]
22:20
slowfranklin has quit [Quit: slowfranklin]
22:53
wcohen has quit [Ping timeout: 268 seconds]