NOTE: If this is a dupe, sorry, but I waited 10+ minutes for the post to appear. Never had a forum take more than 20 seconds to show a thread before, so... Hmm.
I'm having some major stability issues with DTrace under 7.2-RELEASE, on amd64. I followed the wiki to get it working, and it does work, for a few seconds at most.
(By the way, OT, it should be added to the wiki that debug symbols are required to not get an ugly error message!)
When using "opensnoop" from the DTrace toolkit (ports/sysutils/DTraceToolkit, for example), I get this panic:
I'm lazy, so I took a picture of the full screen instead, but being on a forum I hope you've got a graphical browser.
Full info from the second panic: http://www.imgur.com/2nCYu
Steps to replicate, for me:
1) Start opensnoop
2) Do anything that opens a file, it seems (in this case I just did find /var or something to that matter, and it panicked within a second).
/var/crash/info.1:
I haven't done much poking around with other/custom scripts, although a simple
appears stable.
I'm guessing this is related to DTrace not being fully implemented in userland or something like that?
Anyways, any help (or info, for that matter) is appreciated.
I'm having some major stability issues with DTrace under 7.2-RELEASE, on amd64. I followed the wiki to get it working, and it does work, for a few seconds at most.
(By the way, OT, it should be added to the wiki that debug symbols are required to not get an ugly error message!)
When using "opensnoop" from the DTrace toolkit (ports/sysutils/DTraceToolkit, for example), I get this panic:
Code:
Fatal trap 10: trace trap while in kernel mode
... some more info ...
cpuid = 0, apci id = 00
processor eflags: trace trap, nested task, IOPL = 3
current process = mktemp
panic: trace trap
I'm lazy, so I took a picture of the full screen instead, but being on a forum I hope you've got a graphical browser.
Full info from the second panic: http://www.imgur.com/2nCYu
Steps to replicate, for me:
1) Start opensnoop
2) Do anything that opens a file, it seems (in this case I just did find /var or something to that matter, and it panicked within a second).
/var/crash/info.1:
Code:
Dump header from device /dev/ad0s1b
Architecture: amd64
Architecture Version: 2
Dump Length: 729923584B (696 MB)
Blocksize: 512
Dumptime: Fri May 8 09:34:07 2009
Hostname: chaos.exscape.org
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.2-RELEASE #1: Thu May 7 21:01:25 CEST 2009
root@chaos.exscape.org:/usr/obj/usr/src/sys/DTRACE
Panic String: trace trap
Dump Parity: 224395085
Bounds: 1
Dump Status: good
I haven't done much poking around with other/custom scripts, although a simple
Code:
dtrace -n 'syscall:::entry { @a[probefunc] = count(); }'
I'm guessing this is related to DTrace not being fully implemented in userland or something like that?
Anyways, any help (or info, for that matter) is appreciated.