From: Keith Owens <kaos@ocs.com.au>
To: Mohanan P G <pgm@krec.ernet.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Panic on boot (Intel system )
Date: Wed, 25 Jul 2001 21:21:27 +1000 [thread overview]
Message-ID: <9148.996060087@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 25 Jul 2001 05:43:18 +0530." <Pine.LNX.4.30.0107250542190.2447-100000@nanda.krec.ernet.in>
On Wed, 25 Jul 2001 05:43:18 +0530 (IST),
Mohanan P G <pgm@krec.ernet.in> 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.
prev parent reply other threads:[~2001-07-25 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 0:13 Panic on boot (Intel system ) Mohanan P G
2001-07-25 11:21 ` Keith Owens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9148.996060087@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pgm@krec.ernet.in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.