From: Viral Mehta <viral.mehta@einfochips.com>
To: Shivdas Gujare <shivdas.tech@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Understanding kernel Oops while using M-USB
Date: Fri, 15 May 2009 18:27:44 +0530 [thread overview]
Message-ID: <4A0D66C8.4000902@einfochips.com> (raw)
In-Reply-To: <cf70f0210905142347y7738d194k5a616e7d9e4bf092@mail.gmail.com>
Shivdas Gujare wrote:
> Following is a part of Oops on BeagleBoard, which I am trying to understand...
> I have pasted complete Oops at http://pastie.org/478896
>
> [<c0036d24>] (omap3_pm_idle+0x0/0x120) from [<c002c184>] (cpu_idle+0x40/0x60)
> [<c002c144>] (cpu_idle+0x0/0x60) from [<c0299bfc>] (rest_init+0x58/0x6c)
> r5:c037ee8c r4:c0387d38
> [<c0299ba4>] (rest_init+0x0/0x6c) from [<c0008a00>] (start_kernel+0x260/0x2b8)
> [<c00087a0>] (start_kernel+0x0/0x2b8) from [<80008034>] (0x80008034)
>
> --------------------end of oops------------------
> c00087a0(virtual address of start_kernel) + 0x260(offset) = c0008a00
> (value in square bracket above)
> where c0008a00 is the address of next instruction after branch
> instruction to c0299ba4(i.e rest_init)
>
> But here, I didn't understood what is 0x2b8 from
> (start_kernel+0x260/0x2b8). i.e. 0x260 is a offset from start_kernel
> but what is 0x2b8?
>
0x2b8 is a function size.
> Also what address 0x80008034 points to?
>
> I tried to analyze this using "arm-none-linux-gnueabi-objdump -D vmlinux".
>
> I what general scenarios "Unable to handle kernel paging request at
> virtual address" this message gets printed?
>
vim your_kernel_src_dir/Documentation/oops-tracing.txt
--
Thanks, Viral Mehta, Embedded Software Engineer, www.einfochips.com
prev parent reply other threads:[~2009-05-15 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 6:47 Understanding kernel Oops while using M-USB Shivdas Gujare
2009-05-15 12:57 ` Viral Mehta [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=4A0D66C8.4000902@einfochips.com \
--to=viral.mehta@einfochips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shivdas.tech@gmail.com \
/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