H,
i''ve been trying to trace setup_ddi() without any success ...
| [118833-17]# cat setup_ddi.d
| #pragma D option flowindent
|
| setup_ddi:entry
| {
| self->trace = 1;
| }
|
| fbt:::entry
| / self->trace == 1 /
| {}
|
| fbt:::return
| / self->trace == 1 /
| {}
|
| setup_ddi:return
| {
| self->trace = 0;
| }
| [118833-17]#
i''ve passed the script to anonymous tracing
| [118833-17]# dtrace -AFs setup_ddi.d
| dtrace: cleaned up old anonymous enabling in /kernel/drv/dtrace.conf
| dtrace: cleaned up forceload directives in /etc/system
| dtrace: saved anonymous enabling in /kernel/drv/dtrace.conf
| dtrace: added forceload directives to /etc/system
| dtrace: run update_drv(1M) or reboot to enable changes
| [118833-17]#
but when i reboot the system and tried to extract the data,
| [118833-17]# dtrace -a
| dtrace: could not enable tracing: No anonymous tracing state
| [118833-17]#
help ...
Thanks!
sam
On Mon, Aug 14, 2006 at 05:43:10PM +0800, sang-suan gam wrote:> i''ve passed the script to anonymous tracing > > | [118833-17]# dtrace -AFs setup_ddi.d > | dtrace: cleaned up old anonymous enabling in /kernel/drv/dtrace.conf > | dtrace: cleaned up forceload directives in /etc/system > | dtrace: saved anonymous enabling in /kernel/drv/dtrace.conf > | dtrace: added forceload directives to /etc/system > | dtrace: run update_drv(1M) or reboot to enable changes > | [118833-17]# > > but when i reboot the system and tried to extract the data, > > | [118833-17]# dtrace -a > | dtrace: could not enable tracing: No anonymous tracing state > | [118833-17]#Did you get any "enabling probe" messages on the console during boot? What is the output of: echo "::system" | mdb -k on the system? Cheers, - jonathan -- Jonathan Adams, Solaris Kernel Development
Thanks Jonathan, the output is: [118833-17]# echo "::system" | mdb -k forceload: drv/systrace forceload: drv/sdt forceload: drv/profile forceload: drv/lockstat forceload: drv/fbt forceload: drv/fasttrap forceload: drv/dtrace [118833-17]# [118833-17]# Thanks, sam Jonathan Adams wrote:> On Mon, Aug 14, 2006 at 05:43:10PM +0800, sang-suan gam wrote: >> i''ve passed the script to anonymous tracing >> >> | [118833-17]# dtrace -AFs setup_ddi.d >> | dtrace: cleaned up old anonymous enabling in /kernel/drv/dtrace.conf >> | dtrace: cleaned up forceload directives in /etc/system >> | dtrace: saved anonymous enabling in /kernel/drv/dtrace.conf >> | dtrace: added forceload directives to /etc/system >> | dtrace: run update_drv(1M) or reboot to enable changes >> | [118833-17]# >> >> but when i reboot the system and tried to extract the data, >> >> | [118833-17]# dtrace -a >> | dtrace: could not enable tracing: No anonymous tracing state >> | [118833-17]# > > Did you get any "enabling probe" messages on the console during boot? What > is the output of: > > echo "::system" | mdb -k > > on the system? > > Cheers, > - jonathan >
On Tue, Aug 15, 2006 at 02:42:30AM +0800, sang-suan gam wrote:> Thanks Jonathan, > > the output is: > > [118833-17]# echo "::system" | mdb -k > > forceload: drv/systrace > forceload: drv/sdt > forceload: drv/profile > forceload: drv/lockstat > forceload: drv/fbt > forceload: drv/fasttrap > forceload: drv/dtrace > [118833-17]# [118833-17]# >What are your boot arguments? Are you booting an alternate kernel? Were there any "enabling probe n" messages on the console during boot? Cheers, - jonathan> Jonathan Adams wrote: > >On Mon, Aug 14, 2006 at 05:43:10PM +0800, sang-suan gam wrote: > >>i''ve passed the script to anonymous tracing > >> > >> | [118833-17]# dtrace -AFs setup_ddi.d > >> | dtrace: cleaned up old anonymous enabling in /kernel/drv/dtrace.conf > >> | dtrace: cleaned up forceload directives in /etc/system > >> | dtrace: saved anonymous enabling in /kernel/drv/dtrace.conf > >> | dtrace: added forceload directives to /etc/system > >> | dtrace: run update_drv(1M) or reboot to enable changes > >> | [118833-17]# > >> > >>but when i reboot the system and tried to extract the data, > >> > >> | [118833-17]# dtrace -a > >> | dtrace: could not enable tracing: No anonymous tracing state > >> | [118833-17]# > > > >Did you get any "enabling probe" messages on the console during boot? What > >is the output of: > > > > echo "::system" | mdb -k > > > >on the system? > > > >Cheers, > >- jonathan > >-- Jonathan Adams, Solaris Kernel Development
Hi Jonathan, thanks again for looking at this ...> What are your boot arguments? Are you booting an alternate kernel? > Were there any "enabling probe n" messages on the console during boot?i didn''t supply any boot flags and upon bootup, i checked the /etc/system that they contain the forceloads for the various dtrace modules... the bootup messages include: | Aug 14 16:06:24 v4u-4800c-doma pseudo: [ID 129642 kern.info] pseudo-device: systrace0 | Aug 14 16:06:24 v4u-4800c-doma genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace at 0 | Aug 14 16:06:24 v4u-4800c-doma pseudo: [ID 129642 kern.info] pseudo-device: sdt0 | Aug 14 16:06:24 v4u-4800c-doma genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt at 0 | Aug 14 16:06:24 v4u-4800c-doma pseudo: [ID 129642 kern.info] pseudo-device: profile0 | Aug 14 16:06:24 v4u-4800c-doma genunix: [ID 936769 kern.info] profile0 is /pseudo/profile at 0 | Aug 14 16:06:24 v4u-4800c-doma pseudo: [ID 129642 kern.info] pseudo-device: lockstat0 | Aug 14 16:06:24 v4u-4800c-doma genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat at 0 | Aug 14 16:06:24 v4u-4800c-doma pseudo: [ID 129642 kern.info] pseudo-device: fbt0 | Aug 14 16:06:24 v4u-4800c-doma genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt at 0 | Aug 14 16:06:24 v4u-4800c-doma pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0 | Aug 14 16:06:24 v4u-4800c-doma genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap at 0 | Aug 14 16:06:24 v4u-4800c-doma pseudo: [ID 129642 kern.info] pseudo-device: dtrace0 | Aug 14 16:06:24 v4u-4800c-doma genunix: [ID 936769 kern.info] dtrace0 is /pseudo/dtrace at 0 | Aug 14 16:06:24 v4u-4800c-doma dtrace: [ID 566105 kern.notice] NOTICE: enabling probe 0 (::setup_ddi:entry) | Aug 14 16:06:24 v4u-4800c-doma dtrace: [ID 566105 kern.notice] NOTICE: enabling probe 1 (fbt:::entry) | Aug 14 16:06:24 v4u-4800c-doma dtrace: [ID 566105 kern.notice] NOTICE: enabling probe 2 (fbt:::return) | Aug 14 16:06:24 v4u-4800c-doma dtrace: [ID 566105 kern.notice] NOTICE: enabling probe 3 (::setup_ddi:return) | Aug 14 16:06:24 v4u-4800c-doma dtrace: [ID 566105 kern.notice] NOTICE: enabling probe 4 (dtrace:::ERROR) Thanks, cheers, sam