Re: Panic on boot (Intel system )

[Keith Owens]

On Wed, 25 Jul 2001 05:43:18 +0530 (IST), 
Mohanan P G <[e-mail]> wrote:
>Stack: c1254000 00000286 00000004 00000000 c0119e6d 00000004 c1255f38 c1254558
>       c1254000 00000286 00000004 c0119f1c 00000004 c1255f38 c1254000 c1254000
>       00000286 00000000 00000004 c0119fb9 00000004 c1255f38 c1254000 c1254000
>CallTrace: [<c0119e6d>] [<c0119f1c>] [<c0119fb9>] [<c0107244>] [<c01072a3>] [<c012026d>] [<c01202b1>]
>[<c0106c4c>]
>Code c7 01 00 00 00 00 8b 45 04 89 08 89 4d 04 85 f6 74 07 83 fe
>Stack: c1254000 00000286 00000004 00000000 c0119e6d 00000004 c1255f38 c1254558
>       c1254000 00000286 00000004 c0119f1c 00000004 c1255f38 c1254000 c1254000
>       00000286 00000000 00000004 c0119fb9 00000004 c1255f38 c1254000 c1254000
>[<c0106c4c>]
>Warning (Oops_read): Code line not seen, dumping what data is available

Your oops text is not in quite the right format.  ksymoops looks for
'Call Trace:' (space between Call and Trace:) and 'Code:' (: after
Code).  If you adjust your text to match what the kernel actually
produced then rerun ksymoops you will get a better oops report.  Please
send the clean oops report to linux-kernel, not to me.