Re: [PATCH 1/1] x86/oprofile: Fix the calltrace upon profiling some specified events with oprofile

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

Re: [PATCH 1/1] x86/oprofile: Fix the calltrace upon profiling some specified events with oprofile

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

Re: [PATCH] x86, 32-bit: Fix invalid stack address while in softirq

On 09/06/2012 11:54 PM, Steven Rostedt wrote: On Thu, 2012-09-06 at 17:36 +0200, Robert Richter wrote: I meant: unsigned long kernel_stack_pointer(struct pt_regs *regs) { unsigned long context = (unsigned long)regs& ~(THREAD_SIZE - 1); unsigned long sp = (unsigned long)®s->sp;

oops in x86/oprofile/dump_stack with 3.4.6

Hi all, A couple of days ago I tried to use oprofile with enabling call graph in a recent build of 3.4.6. this causes a OOPS "BUG: unable to handle kernel paging request at 636f7270". The oops can be often reproduced by the following steps on my board based on Intel Atom. opcontrol --no-vml