From mboxrd@z Thu Jan  1 00:00:00 1970
From: chris@basementcode.com (Christopher Harvey)
Date: Mon, 29 Aug 2011 08:49:27 -0500
Subject: question about oops and panic
In-Reply-To: <CAOXENUgt1dk4qQwiuR6JO867Saw=q+oZW+V-dGUSjn5=fQSAWg@mail.gmail.com>
References: <CAOXENUgt1dk4qQwiuR6JO867Saw=q+oZW+V-dGUSjn5=fQSAWg@mail.gmail.com>
Message-ID: <7b4b1cba8f2d881976192c49c6fc1a9b@basementcode.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Mon, 29 Aug 2011 01:19:00 +0800, Parmenides wrote:
> Hi,
>
[snip]
>
> Aug 29 00:58:45 lfs kernel: Call Trace:
> Aug 29 00:58:45 lfs kernel:  [<c100112d>] ? 
> do_one_initcall+0x44/0x120
> Aug 29 00:58:45 lfs kernel:  [<c10517ce>] ? 
> sys_init_module+0xa7/0x1d9
> Aug 29 00:58:45 lfs kernel:  [<c138d49d>] ? syscall_call+0x7/0xb
>
> ... ... ...
>
> I wonder what is the meaning of the tow numbers after a function 
> name.
>

You can use objdump -dSl foo.ko to get the exact line that failed. Look 
at the left hand column of the dump and match it with the first hex 
number in your trace. The objdump command may take a while if your 
module is large. Obviously you'll need debugging symbols built into the 
ko.