failed to resolve curpsinfo #62
Comments
|
remove the installed dir /usr/lib/dtrace - the installed *.d files will On 3 August 2013 12:38, Michael Mior notifications@github.com wrote:
|
|
I now get the following. I don't know enough about DTrace to know if the final line is an issue, but removing |
|
what os is this? What does /proc/dtrace/trace show? if you get no device, it may have panicced itself. On 4 August 2013 05:37, Michael Mior notifications@github.com wrote:
|
|
Ubuntu 13.04 with kernel version 3.8.0-27. Here's the entirety of |
|
is this a VM? Is there anything in /var/log/kern.log or dmesg output? Does tx On 4 August 2013 13:10, Michael Mior notifications@github.com wrote:
|
|
Nope, not a VM. I get the following in Then I see this when trying to run the test probe |
|
If this happens, the driver has disabled itself. You can reload the driver On 4 August 2013 21:35, Paul Fox paul.d.fox@gmail.com wrote:
|
|
I've always run |
|
Michael - thanks for this. I wander if this problem shows up on real HW - I The stack trace is showing the cross-cpu call not doing what it should, so Out of interest - is your system running under Xen? Is it Intel or AMD cpu? thanks On 5 August 2013 22:38, Michael Mior notifications@github.com wrote:
|
|
Thanks for helping look into this. Not running under Xen. CPU is AMD E2-3000M. Unfortunately I'll be out of town the rest of the week so I'll be unable to respond for a few days but I should be able to reply to any further requests over the weekend. |
|
Hello, dtrace -c 'ls' -n 'syscall:::entry /pid == $target/ {@[probefunc] = count();}'parent: waiting for child on Gentoo distribution, kernel version 3.15.2 from Gentoo sources cat /proc/dtrace/trace#0 9425:�4dtracedrv loaded: /dev/dtrace available, dtrace_here=0 nr_cpus=8 I have no idea about what is going on and would appreciate any hints. |
|
I cant say at present - I will need to look and reproduce - I presume the Having spent some time on my strace replacement (ptrace - its documented on Will take a look in the next few days (maybe at the weekend). On 17 September 2014 20:47, lukas999 notifications@github.com wrote:
|
|
Thanks for quick reply. I think this is more general problem since even very basic onliner fails: root # dtrace -n BEGIN ... And just to make sure, the driver is loaded and the device eixsts. lsmod | grep dtrace root # ls -l /dev/dtrace* |
|
Works for me build/dtrace -n BEGIN You need to verify if you are using the right dtrace binary and that it is Assuming this is dtrace4linux (and not an oracle version), then try looking I need to try out on a 3.15 or later kernel. On 18 September 2014 06:04, lukas999 notifications@github.com wrote:
|
|
After a reboot, I may be onse step closer to working dtrace since dtrace prints something out but the message still persists. root # make load root # ./build/dtrace -n BEGIN The devices dtrace, dtrace_ctl, dtrace_helper and dtrace_profile were created. I can try any of earlier kernels. What kernel worked for you? |
|
And one more question - are these four devices enough? Shouldn'n there be any more devices? |
I'm new to DTrace and found this really easy to install, but just a basic test probe isn't working
Running Ubuntu 13.04 with kernel version 3.8.0-27. Any help appreciated :)
The text was updated successfully, but these errors were encountered: