The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: tomlins@cam.org, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] uart_block_til_ready 2.5.63
Date: Tue, 25 Feb 2003 01:49:55 -0800	[thread overview]
Message-ID: <20030225014955.3b559ce2.akpm@digeo.com> (raw)
In-Reply-To: <20030225093544.B9257@flint.arm.linux.org.uk>

Russell King <rmk@arm.linux.org.uk> wrote:
>
> On Mon, Feb 24, 2003 at 09:42:25PM -0500, Ed Tomlinson wrote:
> > Feb 24 21:14:44 oscar kernel: Code: f6 80 1c 01 00 00 02 75 2d 8b 4d 08 51 e8 10 6e 00 00 85 c0
> 
> Can someone decode this Code: line into something useful please?

You can just feed that single line into ksymooops.  As long
as you have an x86 machine ;)

mnm:/home/akpm> echo "Code: f6 80 1c 01 00 00 02 75 2d 8b 4d 08 51 e8 10 6e 00 00 85 c0" | ksymoops
....

Code;  00000000 Before first symbol
00000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   f6 80 1c 01 00 00 02      testb  $0x2,0x11c(%eax)
Code;  00000007 Before first symbol
   7:   75 2d                     jne    36 <_EIP+0x36>
Code;  00000009 Before first symbol
   9:   8b 4d 08                  mov    0x8(%ebp),%ecx
Code;  0000000c Before first symbol
   c:   51                        push   %ecx
Code;  0000000d Before first symbol
   d:   e8 10 6e 00 00            call   6e22 <_EIP+0x6e22>
Code;  00000012 Before first symbol
  12:   85 c0                     test   %eax,%eax


1 warning and 1 error issued.  Results may not be reliable.

  reply	other threads:[~2003-02-25  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25  2:42 [OOPS] uart_block_til_ready 2.5.63 Ed Tomlinson
2003-02-25  9:35 ` Russell King
2003-02-25  9:49   ` Andrew Morton [this message]
2003-02-25 16:07   ` Randy.Dunlap

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=20030225014955.3b559ce2.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=tomlins@cam.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