Created
June 19, 2012 14:00
-
-
Save schmurfy/2954385 to your computer and use it in GitHub Desktop.
dtrace4linux
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [ 9833.357917] Kernel panic - not syncing: Attempted to kill the idle task! | |
| [ 9833.359075] Pid: 0, comm: swapper/1 Tainted: P D W O 3.2.0-23-virtual #36-Ubuntu | |
| [ 9833.360463] Call Trace: | |
| [ 9833.360910] [] panic+0x91/0x1a4 | |
| [ 9833.361749] [] do_exit+0x41e/0x420 | |
| [ 9833.362645] [] oops_end+0xb0/0xf0 | |
| [ 9833.363503] [] no_context+0x150/0x15d | |
| [ 9833.364584] [] __bad_area_nosemaphore+0x1c9/0x1e8 | |
| [ 9833.365682] [] ? resched_task+0x2c/0x80 | |
| [ 9833.366645] [] bad_area_nosemaphore+0x13/0x15 | |
| [ 9833.367708] [] do_page_fault+0x426/0x520 | |
| [ 9833.368713] [] ? kvm_clock_read+0x19/0x20 | |
| [ 9833.369697] [] ? kvm_clock_get_cycles+0x9/0x10 | |
| [ 9833.370757] [] ? ktime_get+0x65/0xe0 | |
| [ 9833.371657] [] ? lapic_next_event+0x1d/0x30 | |
| [ 9833.372770] [] ? clockevents_program_event+0x74/0x100 | |
| [ 9833.373999] [] ? timerqueue_add+0x74/0xc0 | |
| [ 9833.375001] [] ? tick_program_event+0x24/0x30 | |
| [ 9833.376087] [] ? pvclock_clocksource_read+0x55/0xf0 | |
| [ 9833.377230] [] page_fault+0x25/0x30 | |
| [ 9833.378136] [] ? native_safe_halt+0xb/0x10 | |
| [ 9833.379135] [] default_idle+0x53/0x1d0 | |
| [ 9833.380111] [] cpu_idle+0xd6/0x120 | |
| [ 9833.381001] [] start_secondary+0xd9/0xdb |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ubuntu@main:~/dtrace$ make install | |
| . build/config.sh ; \ | |
| mkdir -p ""/usr/lib/dtrace/$CPU_BITS ; \ | |
| rm -f ""/usr/lib/dtrace/types.d ; \ | |
| mkdir -p ""/usr/sbin/ ; \ | |
| install -m 4755 -o root build/dtrace ""/usr/sbin/dtrace ; \ | |
| install -m 644 -o root build/drti.o ""/usr/lib/dtrace/$CPU_BITS/drti.o | |
| mkdir: cannot create directory `/usr/lib/dtrace': Permission denied | |
| install: cannot create regular file `/usr/sbin/dtrace': Permission denied | |
| install: cannot create regular file `/usr/lib/dtrace/64/drti.o': No such file or directory | |
| make: *** [install] Error 1 | |
| ubuntu@main:~/dtrace$ sudo make install | |
| . build/config.sh ; \ | |
| mkdir -p ""/usr/lib/dtrace/$CPU_BITS ; \ | |
| rm -f ""/usr/lib/dtrace/types.d ; \ | |
| mkdir -p ""/usr/sbin/ ; \ | |
| install -m 4755 -o root build/dtrace ""/usr/sbin/dtrace ; \ | |
| install -m 644 -o root build/drti.o ""/usr/lib/dtrace/$CPU_BITS/drti.o | |
| mkdir -p ""/etc/ ; \ | |
| if [ ! -f ""/etc/dtrace.conf ] ; then \ | |
| install -m 644 -o root etc/dtrace.conf ""/etc/dtrace.conf ; \ | |
| fi | |
| if [ -f "build/linux-`uname -r`.ctf" ]; then \ | |
| install -m 644 -o root build/linux-`uname -r`.ctf ""/usr/lib/dtrace ; \ | |
| fi | |
| install -m 644 -o root etc/io.d ""/usr/lib/dtrace | |
| install -m 644 -o root etc/sched.d ""/usr/lib/dtrace | |
| install -m 644 -o root etc/unistd.d ""/usr/lib/dtrace | |
| scripts/mkinstall.pl -o=""/usr/lib/dtrace |
the make_install.sh was just to show where the crash happened (last line shown), it may not be relevant but I included it in any case it could be of some use.
I am in a kvm environment (OpenStack host) and this host was a fresh ubuntu 12.04 install.
To reach the kernel panic I compiled, load and then it occured when I type "make install" (the make_install.sh show it happened at "scripts/mkinstall.pl -o=""/usr/lib/dtrace") but I couldn't reproduce it after I rebooted the VM.
What i normally do is:
$ make all
$ make load
I rarely do the "make install" as that perturbs the environment you are in
(which I dont want to, since I am developing and changing).
The mkinstall.pl almost does nothing except copy files, so, I am presuming
that dtrace was loaded, and a page fault caused the kernel panic.
I run dtrace on 12.04 - its possible theres a latent bug, but also,
possibly and more likely, the kvm environment might be causing an issue.
Do you have a link for openstack so I can attempt to reproduce your
environment?
tx
…On 21 June 2012 15:48, Julien Ammous < ***@***.*** > wrote:
the make_install.sh was just to show where the crash happened (last line
shown), it may not be relevant but I included it in any case it could be of
some use.
I am in a kvm environment (OpenStack host) and this host was a fresh
ubuntu 12.04 install.
To reach the kernel panic I compiled, load and then it occured when I type
"make install" (the make_install.sh show it happened at "scripts/
mkinstall.pl -o=""/usr/lib/dtrace") but I couldn't reproduce it after I
rebooted the VM.
---
Reply to this email directly or view it on GitHub:
https://gist.github.com/2954385
OpenStack is basically a manager built upon on top of the existing linux tools: kvm, libvirt amongst others, I use it on he physical host to manage the VMs.
The VM are kvm processes spanwed via libvirt from what I can tell.
If you ever want to install it here is a good guide: http://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolin
I got another kernel panic but I don't know what caused it, the VM was mostly idle and when I tried to log into after some time it was crashed but there was nothing in the logs except a message mentioning dtracedrv.
Great - thanks. I strongly suspect a problem with KVM. All of my testing
was with vmware and virtualbox. I know, in looking at the virtualised
kernel sections, a lot of areas I was unsure about - this might be an
example.
A potential problem is that dtrace may rely on certain kernel functions
leading to reentrancy issues (especially in the crit path of interrupts and
faults). The fact you are seeing this "out of the blue" is probably a sign
that any page fault is triggering an API violation - so that is useful.
I havent used KVM in a long while, so may be I should.
You are having this problem inside your guest or your host?
…On 21 June 2012 16:45, Julien Ammous < ***@***.*** > wrote:
OpenStack is basically a manager built upon on top of the existing linux
tools: kvm, libvirt amongst others, I use it on he physical host to manage
the VMs.
The VM are kvm processes spanwed via libvirt from what I can tell.
If you ever want to install it here is a good guide:
http://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolin
I got another kernel panic but I don't know what caused it, the VM was
mostly idle and when I tried to log into after some time it was crashed but
there was nothing in the logs except a message mentioning dtracedrv.
---
Reply to this email directly or view it on GitHub:
https://gist.github.com/2954385
inside the guest where I installed dtrace, the host is unaffected.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure why you are showing the make_install.sh - you need to be root to install, as you have done.
Your kernel panic is interesting and I am trying to understand the environment you are in. My normal kernels are VMs. Or I run outside a VM on the raw hardware. The calls to kvm functions are possibly interesting - maybe you are in a Xen or some other environment?
Ubuntu - all the way back to 8.04 should work, but its possible one of the earlier releases got broken by some fix for a later version.
When does this panic occur - on driver load, or when you are experimenting with dtrace?