Understanding kernel Oops while using M-USB

Understanding kernel Oops while using M-USB

[Shivdas Gujare]

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?
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?


Thanks for your help.

Thanks and Regards,
Shivdas Gujare

Re: Understanding kernel Oops while using M-USB

[Viral Mehta]

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