>Read linux/Documentation/oop-stracing.txt. Without a symbolic dump of
>your call trace, the oops is useless: we can't tell where in the kernel
>it came from. You just need to make sure you preserve the System.map
>which was built with the kernel, and look at the
>linux/scripts/ksymoops.cc program which can interpret the call trace for
>you.
What if the oops occurs early on during boot, i.e. at the onset of init?
MICHAEL Wm. GILBERT mgilbert@oit.umass.edu
Technology Development and Special Projects
Office of Information Technology (OIT)
University of Massachusetts at Amherst
Voice: 413-545-3124 Fax: 413-545-3203
A115 Lederle Graduate Research Center
UMASS Amherst, MA 01003 USA
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/