This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/19001] mdelay() causing soft lockup
- From: "bmr at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 24 Sep 2015 10:45:07 +0000
- Subject: [Bug tapsets/19001] mdelay() causing soft lockup
- Auto-submitted: auto-generated
- References: <bug-19001-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19001
Bryn M. Reeves <bmr at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bmr at redhat dot com
--- Comment #1 from Bryn M. Reeves <bmr at redhat dot com> ---
This is expected when passing -1 as the delay interval: I originally wrote the
tapset to allow controlled simulation of driver bugs that triggered
softlockups.
The guru-delay tapset is useful for introducing (normally short) controlled
delays at specified probe points; if the specified delay interval exceeds the
configured softlockup threshold for the system it will trigger these warnings.
This is the reason the tapset is named 'guru-delay' and requires -g to be used
- Frank suggested this name and restriction during review to prevent an
unprivileged user impacting other system activities.
--
You are receiving this mail because:
You are the assignee for the bug.