Re: PROBLEM: 2.2.5 unstable on Dell PC, 2.0.36 is stable

Keith Owens (kaos@ocs.com.au)
Wed, 04 Aug 1999 20:37:28 +1000

On Wed, 04 Aug 99 11:22:50 +0100,
Richard Black <rjb@dcs.gla.ac.uk> wrote:
>so I modified the 2.2.10 kernel so I could get the registers on the console
>irrespective of the length of the stack output (patches enclosed) by putting
>the registers at the end (also reduced the amount of junk printed around hex
>so one could get more information on the screen). With that change I get the
>following OOPS message/dump.
>
>Call Trace: c0117cf9 c01180e5 c0107f8e c0107f93 c010f23c c01e302e

ksymoops expects Call Trace fileds to be enclosed in <[...]>. Make
those fields look like this or ksymoops ignores them.

Call Trace: <[c0117cf9]> <[c01180e5]> <[c0107f8e]>

>Code: c7 05 00 00 00 00 00 00 00 00 8d 65 d8 5b 5e 5f 89 ec 5d c3
>CPU: 0
>EIP 0010:[<c0111786>]

EIP has to come before Code to define where the failing instruction is.
In fact the presence of the Code line tells ksymoops it is the end of
the oops so it can pull everything together and decode the report. The
Code line must be last.

-
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/