From: Keith Owens <kaos@ocs.com.au>
To: Dave Jones <davej@suse.de>
Cc: Lawrence Walton <lawrence@the-penguin.otak.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.9 and 1.5.10 don't boot
Date: Tue, 30 Apr 2002 21:22:23 +1000 [thread overview]
Message-ID: <8949.1020165743@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 30 Apr 2002 13:04:46 +0200." <20020430130445.B22842@suse.de>
On Tue, 30 Apr 2002 13:04:46 +0200,
Dave Jones <davej@suse.de> wrote:
>On Mon, Apr 29, 2002 at 12:02:48PM -0700, Lawrence Walton wrote:
> > unable to handle kernel null pointer deference at address 00000016
> > printing EIP:
> > c0198147
> > Oops:0000
> > CPU: 0
> > EIP: 0010:[<c0198147>] not tainted
> > EFLAGS: 00010213
> > EAX: 00000000 EBX: c17p4ac0 ECX: c17fec00 EDX: 00000088
> > ESI: 00000004 EDI: 00000008 EBX: c17f4ac0 ESP: c16e7dcc
>
>This dump is useless to anyone, as the addresses need to be converted
>to symbol names. The EIP being the more important one, followed by the
>call trace.
>
>If you don't want to have to type out a whole oops to feed to ksymoops,
>you can look up the addresses in the System.map from that kernel.
>Note, there are likely to be addresses that don't resolve. For example,
>you may not find c0198147, but you will see c0198140 and c0198190. In
>this circumstance, take the lower symbol.
'ksymoops -A c0198147' is even easier. It does the work for you.
next prev parent reply other threads:[~2002-04-30 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 19:02 2.5.9 and 1.5.10 don't boot Lawrence Walton
2002-04-30 11:04 ` Dave Jones
2002-04-30 11:22 ` Keith Owens [this message]
2002-05-01 0:05 ` 2.5.10 and 2.5.11 not booting Lawrence Walton
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=8949.1020165743@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=davej@suse.de \
--cc=lawrence@the-penguin.otak.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox