On 09/04/2012 06:24 PM, Robert Richter wrote:
Wei,
see my comments below.
On 27.08.12 09:32:13, wei.y...@windriver.com wrote:
From: Wei Yang
Upon enabling the call-graph functionality of oprofile, A few minutes
later the following calltrace will always occur.
BUG: unable to handle kernel pag
Wei,
see my comments below.
On 27.08.12 09:32:13, wei.y...@windriver.com wrote:
> From: Wei Yang
>
> Upon enabling the call-graph functionality of oprofile, A few minutes
> later the following calltrace will always occur.
>
> BUG: unable to handle kernel paging request at 656d6153
> IP: [] pri
On 08/28/2012 05:17 PM, Robert Richter wrote:
On 27.08.12 09:32:13, wei.y...@windriver.com wrote:
From: Wei Yang
Upon enabling the call-graph functionality of oprofile, A few minutes
later the following calltrace will always occur.
BUG: unable to handle kernel paging request at 656d6153
This
On 27.08.12 09:32:13, wei.y...@windriver.com wrote:
> From: Wei Yang
>
> Upon enabling the call-graph functionality of oprofile, A few minutes
> later the following calltrace will always occur.
>
> BUG: unable to handle kernel paging request at 656d6153
This is probably the same I found to yest
From: Wei Yang
Upon enabling the call-graph functionality of oprofile, A few minutes
later the following calltrace will always occur.
BUG: unable to handle kernel paging request at 656d6153
IP: [] print_context_stack+0x55/0x110
*pde =
Oops: [#1] PREEMPT SMP
Modules linked in:
Pid:
5 matches
Mail list logo