fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
_whitelogger has joined #systemtap
hpt has joined #systemtap
khaled has joined #systemtap
lindi- has quit [Ping timeout: 250 seconds]
lindi- has joined #systemtap
orivej has joined #systemtap
orivej has quit [Ping timeout: 245 seconds]
mjw has joined #systemtap
orivej has joined #systemtap
orivej has quit [Ping timeout: 268 seconds]
hpt has quit [Ping timeout: 272 seconds]
przemoc has quit [Ping timeout: 272 seconds]
przemoc has joined #systemtap
orivej has joined #systemtap
orivej has quit [Ping timeout: 245 seconds]
sscox has joined #systemtap
wcohen has quit [Ping timeout: 272 seconds]
tromey has joined #systemtap
sscox has quit [Quit: sscox]
wcohen has joined #systemtap
sscox has joined #systemtap
<agentzh>
fche: thanks for taking care of the vma tracker thing on fed29+.
<agentzh>
but it seems like there's still some other issues on fed29. seeing many mysterious read faults in user_string_n().
<agentzh>
i'll try digging deeper.
dmalcolm has quit [Ping timeout: 246 seconds]
dmalcolm has joined #systemtap
<fche>
that's legit if the user page is not swapped in fwiw.
<agentzh>
i'm pretty sure it's not swapping :)
<fche>
s/swapped/paged/
<agentzh>
i'm sure they are paged.
<agentzh>
it's from our test suite.
<agentzh>
never saw them before.
<agentzh>
like on fed28
<agentzh>
maybe the vma addresses are still wrong in some cases.
<agentzh>
need to prepare an isolated test case.
<agentzh>
our existing failing tests are big, like tracing nginx and luajit.