dtrace discuss - Apr 2006 - Anonymous Tracing and SF T2000

What might have happened if I couldn''t collect the tracing result in
anonymous tracing?  #dtrace -ae <----- nothing comes out.

I wanted to use anonymous tracing to debug and trace activity of the HBA driver
that occurs during system boot. I followed the SDTG doc and use
xxx.d is the script 
#dtrace -AFs xxx.d
#reboot
<system booted>
#dtrace -ae
<nothing> obtained on SunFire T2000  (24 logical CPU)
<expected output> obtained on SunBlade 1500 (single CPU)

I hope some dtrace gurus can explain to me why my anonymous tracing seems to be
working differently on this two machines, at least I couldn''t collect
the trace on T2000.

the same OS verison(nvs35). same HBA driver, same xxx.d script except that I was
using different HBA cards (dual port PCI and PCIX card)
Best Regards,
 
 
This message posted from opensolaris.org

I am also seeing this issue on a T2000.  I wrote a script to trace activity
during attach of the uata module, but saw no output after issuing the
"dtrace -ae" command as was shown in the SDTG.

At first I assumed that the uata module was getting loaded before the dtrace
module, but set moddebug = 0x8000000 in /etc/system to print messages as modules
loaded. This showed that dtrace got loaded right after the modules necessary to
mount the root device and WAY before the uata module was loaded.  So AFAIK,
dtracing the uata attach() routine should have been possible.
 
 
This message posted from opensolaris.org

I see that each time a printa() is being called on an aggregation 
(populated by using the sum function), the output values are always 
sorted by ascending order. Is there a way to alter this behavior? (eg. 
to print an aggregation sorting the values by descending order)

On Mon, Jun 26, 2006 at 10:24:22PM +0200, Alessio Cervellin
wrote:
> I see that each time a printa() is being called on an aggregation 
> (populated by using the sum function), the output values are always 
> sorted by ascending order. Is there a way to alter this behavior? (eg. 
> to print an aggregation sorting the values by descending order)
There are various dtrace options to control this:


	aggsortrev, when set to a non-zero value, will reverse the sort.

	aggsortkey, when set to a non-zero value, will sort by keys instead
	of value

	aggsortkeypos controls which key # to sort by (default is 0).  It
	has no effect unless aggsortkey is active.

	aggsortpos controls which aggregation''s value to sort by;  only
	matters if more than one aggregation is being printed at the
	same time.

See

http://www.opensolaris.org/jive/thread.jspa?messageID=13856

for more information.

Cheers,
- jonathan

-- 
Jonathan Adams, Solaris Kernel Development

Jonathan Adams wrote:
> There are various dtrace options to control this:
> 
> 
> 	aggsortrev, when set to a non-zero value, will reverse the sort.
> 
> 	aggsortkey, when set to a non-zero value, will sort by keys instead
> 	of value
> 
> 	aggsortkeypos controls which key # to sort by (default is 0).  It
> 	has no effect unless aggsortkey is active.
> 
> 	aggsortpos controls which aggregation''s value to sort by;  only
> 	matters if more than one aggregation is being printed at the
> 	same time.
thank you.
do you know which release of solaris 10/dtrace allows these options?

On Mon, Jun 26, 2006 at 10:55:00PM +0200, Alessio Cervellin
wrote:
> Jonathan Adams wrote:
> 
> >There are various dtrace options to control this:
> >
> >
> >	aggsortrev, when set to a non-zero value, will reverse the sort.
> >
> >	aggsortkey, when set to a non-zero value, will sort by keys instead
> >	of value
> >
> >	aggsortkeypos controls which key # to sort by (default is 0).  It
> >	has no effect unless aggsortkey is active.
> >
> >	aggsortpos controls which aggregation''s value to sort by; 
only
> >	matters if more than one aggregation is being printed at the
> >	same time.
> 
> thank you.
> do you know which release of solaris 10/dtrace allows these options?
Solaris Nevada has this already;  it looks like this is not yet available in
Solaris 10.  It''s currently targeting Update 3;  Update 2 was just
released.

Cheers,
- jonathan

-- 
Jonathan Adams, Solaris Kernel Development