From: David Long <dave.long@linaro.org>
To: William Cohen <wcohen@redhat.com>, Pratyush Anand <panand@redhat.com>
Cc: systemtap@sourceware.org, Mark Brown <broonie@linaro.org>,
Jeremy Linton <jlinton@redhat.com>,
David Smith <dsmith@redhat.com>
Subject: Re: exercising current aarch64 kprobe support with systemtap
Date: Thu, 23 Jun 2016 18:26:00 -0000 [thread overview]
Message-ID: <576C29E1.8060805@linaro.org> (raw)
In-Reply-To: <e5f466f7-4a60-efb3-d104-375807d271b2@redhat.com>
On 06/23/2016 11:49 AM, William Cohen wrote:
> On 06/22/2016 11:18 PM, David Long wrote:
>> On 06/22/2016 04:24 PM, William Cohen wrote:
>>> Hi all,
>>>
>>> When running the current systemtap checked out from the git repository
>>> and a locally built kernel with the kprobes64-v13 patches (the
>>> test_upstream_arm64_devel branch of
>>> https://github.com/pratyushanand/linux) on Fedora 23 machine one of
>>> the kprobes_onthefly.exp tests is causing the machine to get in a
>>> state that requires rebooting to fix. This can be triggered by running a
>>> portion of the systemtap tests with:
>>>
>>> make installcheck RUNTESTFLAGS="--debug systemtap.onthefly/kprobes_onthefly.exp"
>>>
>>> When it gets to the kprobes_onthefly - otf_stress_max_iter_5000 test the
>>> console starts spewing the following and needs to be rebooted:
>>>
>>> [23394.036860] Unexpected kernel single-step exception at EL1
>>> [23394.042434] Unexpected kernel single-step exception at EL1
>>> [23394.048008] Unexpected kernel single-step exception at EL1
>>> [23394.053541] Unexpected kernel single-step exception at EL1
>>> [23394.059053] Unexpected kernel single-step exception at EL1
>>> [23394.064545] Unexpected kernel single-step exception at EL1
>>>
>>> Sorry I don't have the start of the failure it scrolled off the screen very quickly.
>>>
>>> -Will
>>>
>>>
>>
>> I'll take a look and see what I can figure out.
>>
>> In the meantime I did just push a v14 branch. I'm doubtful that it will address the above problem even though it contains a few bug fixes.
>>
>> -dl
>>
>
> Hi Dave and Pratyush,
>
> I tried the kprobes64-v13 kernel and it also seems to work, so it lookw like the problem might be in the the
> test_upstream_arm64_devel branch of https://github.com/pratyushanand/linux .
>
> -Will
>
I'm going to interpret that as meaning you know of no problem in the
kprobes v14 patch that would give me pause to email it upstream. Do you
disagree?
-dl
next prev parent reply other threads:[~2016-06-23 18:26 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 16:17 William Cohen
2016-06-09 19:52 ` William Cohen
2016-06-10 3:42 ` David Long
2016-06-10 5:49 ` David Long
2016-06-10 13:43 ` Pratyush Anand
2016-06-10 14:03 ` William Cohen
2016-06-10 14:37 ` David Long
2016-06-10 15:27 ` William Cohen
2016-06-10 14:20 ` David Long
2016-06-10 15:11 ` William Cohen
2016-06-10 17:07 ` Pratyush Anand
2016-07-12 14:33 ` William Cohen
2016-07-13 18:26 ` David Long
2016-07-13 18:47 ` Pratyush Anand
2016-07-13 19:45 ` William Cohen
2016-06-10 21:28 ` William Cohen
2016-06-10 21:37 ` William Cohen
2016-06-13 4:28 ` Pratyush Anand
2016-06-13 13:42 ` William Cohen
2016-06-22 20:24 ` William Cohen
2016-06-23 3:19 ` David Long
2016-06-23 13:42 ` William Cohen
2016-06-23 13:47 ` David Smith
2016-06-23 15:49 ` William Cohen
2016-06-23 18:26 ` David Long [this message]
2016-06-23 19:22 ` William Cohen
2016-06-27 2:57 ` David Long
2016-06-27 14:18 ` Pratyush Anand
2016-06-28 3:20 ` William Cohen
2016-07-04 12:46 ` Pratyush Anand
2016-07-07 19:05 ` David Long
2016-07-07 19:58 ` Frank Ch. Eigler
2016-08-03 13:13 ` Pratyush Anand
2016-08-03 14:51 ` William Cohen
2016-08-03 15:11 ` David Long
2016-08-03 17:40 ` William Cohen
2016-08-03 20:00 ` Lastest kprobes64 patch David Long
2016-08-03 20:01 ` Frank Ch. Eigler
2016-08-03 20:08 ` David Long
2016-08-04 5:03 ` Pratyush Anand
2016-08-04 13:07 ` David Long
2016-08-04 4:42 ` exercising current aarch64 kprobe support with systemtap Pratyush Anand
2016-08-04 13:57 ` William Cohen
2016-08-04 14:36 ` Pratyush Anand
2016-08-04 14:50 ` William Cohen
2016-08-04 20:51 ` William Cohen
2016-08-17 14:36 ` William Cohen
2016-08-17 18:04 ` David Smith
2016-08-17 18:28 ` William Cohen
2016-08-18 15:07 ` David Smith
2016-08-18 15:16 ` William Cohen
2016-08-18 15:39 ` David Smith
2016-08-18 14:55 ` Pratyush Anand
2016-06-13 16:11 ` William Cohen
2016-06-13 16:15 ` William Cohen
2016-06-14 4:27 ` Pratyush Anand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=576C29E1.8060805@linaro.org \
--to=dave.long@linaro.org \
--cc=broonie@linaro.org \
--cc=dsmith@redhat.com \
--cc=jlinton@redhat.com \
--cc=panand@redhat.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).