Have you read Documentation/oops-tracing.txt in your kernel tree? If not,
that would be a good place to start.
> Do i need to run the ksymoops from the same computer which barfed?
It needs access to your System.map, which ought to be in /boot.
> from what i've been able to tell, the output f
I've come across this problem, with the kernel barfing up a bunch of hex
output (stack and other information). None of the output gets saved in
any log files , but i did write down the output on
the screen from the last episode. I am assuming that this is a hardware
problem, and from what i've
