-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic running systrace-stringof-bad, kernel 3.2 #46
Comments
Set a breakpoint on inter.c:625 in kvm/gdb and it was never hit so it appears that DTRACE_CPUFLAG_ISSET(CPU_DTRACE_NOFAULT) is always false. |
I thought I had a semi-coherent bug report, now it seems to be degrading into "nothing works" :( |
Thanks for the report Caleb. I have never tested with KVM - looks like the Thanks for the report (I need to look at your patch as well); may take me a On 16 December 2012 02:43, Caleb James DeLisle notifications@github.comwrote:
|
I have not tested this all the way through but it should work ok. |
Brilliant - thank you Caleb - very useful, especially as you included the On 16 December 2012 10:37, Caleb James DeLisle notifications@github.comwrote:
|
This is a log from it running in a KVM node. I ran the test on my laptop (also 3.2) and got a panic but did not spend the time to hook up a netconsole.
Linux debian 3.2.0-2-amd64 #1 SMP Mon Apr 30 05:20:23 UTC 2012 x86_64 GNU/Linux
I modified the source to build on Debian ( #45 ).
Let me know if there is anything else I can provide. I tried building with dtrace_printf() uncomented in dtrace_int_page_fault_handler() and it paniced in a different way, I suspect calling dtrace_printf() might have triggered another page fault.
Processor on the host is an AMD 6128. The guest is running with -smp 6
In the guest /proc/cpuinfo appears as:
The text was updated successfully, but these errors were encountered: