mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Amir Hermelin" <amir@montilio.com>
To: "'Randy.Dunlap'" <rddunlap@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Format of an 'oops' call trace (in show_trace)
Date: Wed, 8 Oct 2003 13:25:44 +0200	[thread overview]
Message-ID: <018e01c38d8e$efd4a9b0$0401a8c0@CARTMAN> (raw)
In-Reply-To: <20031007122631.4f028e62.rddunlap@osdl.org>

Oops, 
I forgot that part :)  It's RH 2.4.20-8

Thanks,
Amir.

-----Original Message-----
From: Randy.Dunlap [mailto:rddunlap@osdl.org] 
Sent: Tuesday, October 07, 2003 9:27 PM
To: Amir Hermelin
Cc: linux-kernel@vger.kernel.org
Subject: Re: Format of an 'oops' call trace (in show_trace)


On Tue, 7 Oct 2003 17:56:38 +0200 "Amir Hermelin" <amir@montilio.com> wrote:

| Hi,
| Can someone please point me to a description of what I see in the Call 
| of the oops dump?  I tried looking into show_trace and lookup_symbol 
| functions, but I couldn't understand some things.  For example, in 
| this following
| trace:
| Oct  7 17:13:54 joji kernel: [<e01bae00>] reqrdata [mymod] 0x0
(0xd5543fb4))
| 
| Oct  7 17:13:54 joji kernel: [<e01a5220>] mymod [mymod] 0x0 
| (0xd5543fe0))
| I don't understand the relevance to reqrdata (since it's not a function,
but
| a data structure, and isn't the parameter to the mymod function).
| And could
| someone please explain what the 0x0 in the lines mean? From the code I
| understood it to be the offset of the symbol within the module, but that
| can't be right if both symbols translate to the same offset - so I must've
| understood it wrong.

Hi,

What kernel version is this?
Any patches applied to it?

~Randy

| Oct  7 17:13:54 joji kernel:  printing eip:
| Oct  7 17:13:54 joji kernel: e01b090b
| Oct  7 17:13:54 joji kernel: *pde = 00000000
| Oct  7 17:13:54 joji kernel: Oops: 0002
| Oct  7 17:13:54 joji kernel: nfsd nfs lockd sunrpc bcm5700 parport_pc 
| lp parport autofs sg sr_mod ide-scsi scsi_mod ide-cd cdrom key mymod 
| bdev mousedev hid input usb-uhci ehci-hcd usbcore ext3
| Oct  7 17:13:54 joji kernel: CPU:    0
| Oct  7 17:13:54 joji kernel: EIP:    0060:[<e01b090b>]    Not tainted
| Oct  7 17:13:54 joji kernel: EFLAGS: 00010282
| Oct  7 17:13:54 joji kernel:
| Oct  7 17:13:54 joji kernel: EIP is at rtp_recv [mymod] 0x5b
| (2.4.20-8custom)
| Oct  7 17:13:54 joji kernel: eax: 00000000   ebx: d5542000   ecx: 00000001
| edx: c0374c88
| Oct  7 17:13:54 joji kernel: esi: e01bae00   edi: d76aa400   ebp: d5543fcc
| esp: d5543f98
| Oct  7 17:13:54 joji kernel: ds: 0068   es: 0068   ss: 0068
| Oct  7 17:13:54 joji kernel: Process mymod (pid: 6978, stackpage=d5543000)

| Oct  7 17:13:54 joji kernel: Stack: e01bae00 d76aa400 d5542000 00000000
| d76aa400 ffffffff e01a5308 e01bae00 
| Oct  7 17:13:54 joji kernel:        d76aa400 d5543fcc d5542000 d5542000
| dbd15900 00000000 d54f3fd0 d5533fd0 
| Oct  7 17:13:54 joji kernel:        d5542000 00000000 e01a5220 00000000
| 00000000 00000000 c010742d d76aa400 
| Oct  7 17:13:54 joji kernel: Call Trace:   [<e01bae00>] reqrdata [mymod]
0x0
| (0xd5543f98))
| Oct  7 17:13:54 joji kernel: [<e01a5308>] mymod [mymod] 0xe8 (0xd5543fb0))

| Oct  7 17:13:54 joji kernel: [<e01bae00>] reqrdata [mymod] 0x0
(0xd5543fb4))
| 
| Oct  7 17:13:54 joji kernel: [<e01a5220>] mymod [mymod] 0x0 
| (0xd5543fe0))
| Oct  7 17:13:54 joji kernel: [<c010742d>] kernel_thread_helper [kernel]
0x5
| (0xd5543ff0)) 
| Oct  7 17:13:54 joji kernel: 
| Oct  7 17:13:54 joji kernel: 
| Oct  7 17:13:54 joji kernel: Code: ff 40 1c 8b 56 10 8b 52 1c 89 97 98 01
00
| 00 01 50 24 89 7c 



  reply	other threads:[~2003-10-08 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 15:56 Amir Hermelin
2003-10-07 19:26 ` Randy.Dunlap
2003-10-08 11:25   ` Amir Hermelin [this message]
2003-10-08 17:06     ` Randy.Dunlap
2003-10-09 17:20       ` Amir Hermelin
2003-10-10 22:52         ` 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='018e01c38d8e$efd4a9b0$0401a8c0@CARTMAN' \
    --to=amir@montilio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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

Powered by JetHome