panic on fedora 18 while trying to run "make test" about linux HOT 2 OPEN

This was my experience last time I tried dtrace on my laptop and in a kvm.
If you run netconsole and catch the error on another machine, it might provide some insite into what's actually going on but this is information that I can't make much sense of, have to wait until paul has more free time or another kernel guy comes along...
https://www.kernel.org/doc/Documentation/networking/netconsole.txt
Thanks,
Caleb

from linux.

when running 'make test' which really is a torture test - its best to try
and figure out which test is failing - keep an eye on the screen. its also
a good idea to avoid running X windows and do this at the console (easier
to see any panics). Its not nice to panic your machine, so my apologies -
this could be a stupid issue from a recent update - or some new unhandled
kernel issue (I dont think i have tried FC18 yet).

The torture test really tries to exercise every CPU and trigger lots of
syscall activity.

'make test' runs a perl script so you can run each test individually to
narrow it down, but other than reporting the bug, theres probably little
you can do to self-help (other than not run the tests). The torture test is
designed to give you confidence in dtrace and hit issues quickly rather
than leave you exposed.

On 5 March 2013 13:57, Caleb James DeLisle [email protected] wrote:

This was my experience last time I tried dtrace on my laptop and in a kvm.
If you run netconsole and catch the error on another machine, it might
provide some insite into what's actually going on but this is information
that I can't make much sense of, have to wait until paul has more free time
or another kernel guy comes along...
https://www.kernel.org/doc/Documentation/networking/netconsole.txt
Thanks,
Caleb

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/52#issuecomment-14440944
.

from linux.