>From my limited understanding, there are 2 kinds of speculation
related failures that are seen:
Failures due to insufficient number of buffers (no speculative buffer
available) and failures due to using a buffer that is busy getting
discarded/committed (available buffer(s) still busy)
For the former consider increasing the number of buffers with the
nspec option. For the latter, consider setting the CPU cleanrate to
value beyond the default (101)
The "Abort due to systemic unresponsiveness" indicates heavy load.
This if addressed will probably not throw the "error on enabled probe"
error assuming data access is happening right.
When is the speculative buffer created? When is it committed? Can the
paths being speculated be reduced?
-Shiv
On Sun, Nov 16, 2008 at 6:37 AM, tester <[EMAIL PROTECTED]> wrote:
> system is Solaris 10 11/06 s10s_u3wos_10 SPARC on a frame.
>
> I running speculative tracing for fork* and have this cluse for fbt
>
> fbt:::
> /self->spec/
> {
> /*
> * A speculate() with no other actions speculates the default action:
> * tracing the EPID.
> */
> speculate(self->spec);
> }
>
> I had the following messages which ended with abort message.
>
> dtrace: 5 failed speculations (no speculative buffer available)
> dtrace: error on enabled probe ID 1 (ID 3068: syscall::fork1:entry): invalid
> address (0x0) in action #3 at DIF offset 28
> dtrace: error on enabled probe ID 1 (ID 3068: syscall::fork1:entry): invalid
> address (0x0) in action #3 at DIF offset 28
> dtrace: error on enabled probe ID 1 (ID 3068: syscall::fork1:entry): invalid
> address (0x0) in action #3 at DIF offset 28
> dtrace: 1 failed speculation (available buffer(s) still busy)
> dtrace: 5 failed speculations (no speculative buffer available)
> dtrace: 1 failed speculation (no speculative buffer available)
> dtrace: 1 failed speculation (no speculative buffer available)
> dtrace: 2 failed speculations (no speculative buffer available)
> dtrace: processing aborted: Abort due to systemic unresponsiveness
>
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
