dtrace discuss - Nov 2007 - dtrace errors

Hi,

I came across a tons of errors while running Dtrace:

dtrace: error on enabled probe ID 30 (ID 38220:
plockstat3862:libc.so.1:mutex_unlock_queue:mutex-release): illegal operation in
action #3
dtrace: error on enabled probe ID 26 (ID 17: sysinfo:unix:swtch:pswitch):
illegal operation in action #3
dtrace: error on enabled probe ID 26 (ID 17: sysinfo:unix:swtch:pswitch):
illegal operation in action #3
dtrace: error on enabled probe ID 13 (ID 37780:
plockstat3862:libc.so.1:cond_wait_queue:mutex-acquire): illegal operation in
action #3
dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
dtrace: error on enabled probe ID 6 (ID 37787:
plockstat3862:libc.so.1:mutex_lock_queue:mutex-acquire): illegal operation in
action #3
dtrace: error on enabled probe ID 4 (ID 37789:
plockstat3862:libc.so.1:mutex_trylock_adaptive:mutex-acquire): illegal operation
in action #3
dtrace: error on enabled probe ID 26 (ID 17: sysinfo:unix:swtch:pswitch):
illegal operation in action #3
dtrace: error on enabled probe ID 26 (ID 17: sysinfo:unix:swtch:pswitch):
illegal operation in action #3

Does anyone have a clue, what are these about?

Thanks,
Neelam


--
This message posted from opensolaris.org

It would be helpful if you''d send the script that you''re
using.

Adam

On Sun, Nov 25, 2007 at 12:19:51PM -0800, Neelam wrote:
> Hi,
> 
> I came across a tons of errors while running Dtrace:
> 
> dtrace: error on enabled probe ID 30 (ID 38220:
plockstat3862:libc.so.1:mutex_unlock_queue:mutex-release): illegal operation in
action #3
> dtrace: error on enabled probe ID 26 (ID 17: sysinfo:unix:swtch:pswitch):
illegal operation in action #3
> dtrace: error on enabled probe ID 26 (ID 17: sysinfo:unix:swtch:pswitch):
illegal operation in action #3
> dtrace: error on enabled probe ID 13 (ID 37780:
plockstat3862:libc.so.1:cond_wait_queue:mutex-acquire): illegal operation in
action #3
> dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
> dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
> dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
> dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
> dtrace: error on enabled probe ID 9 (ID 37784:
plockstat3862:libc.so.1:mutex_lock_impl:mutex-acquire): illegal operation in
action #3
> dtrace: error on enabled probe ID 6 (ID 37787:
plockstat3862:libc.so.1:mutex_lock_queue:mutex-acquire): illegal operation in
action #3
> dtrace: error on enabled probe ID 4 (ID 37789:
plockstat3862:libc.so.1:mutex_trylock_adaptive:mutex-acquire): illegal operation
in action #3
> dtrace: error on enabled probe ID 26 (ID 17: sysinfo:unix:swtch:pswitch):
illegal operation in action #3
> dtrace: error on enabled probe ID 26 (ID 17: sysinfo:unix:swtch:pswitch):
illegal operation in action #3
> 
> Does anyone have a clue, what are these about?
> 
> Thanks,
> Neelam
> 
> 
> --
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
-- 
Adam Leventhal, FishWorks                        http://blogs.sun.com/ahl

I think I had a problem with aggregation functions. After I got rid of some of
them, the errors were gone. I was using the same vector name for more than one
probe.

e.g. @value=avg(something); in more than one probe. Is that a problem? I thought
that it should count for both the probes!


--
This message posted from opensolaris.org