Messages in this thread | | | Date | Fri, 24 May 2013 10:23:38 -0400 | From | Dave Jones <> | Subject | Re: rcu_read_lock() used illegally while idle! |
| |
On Fri, May 24, 2013 at 09:46:20AM -0400, Steven Rostedt wrote:
> > > This looks to be the caused by the same issue that this patch fixes: > > > > > > https://lkml.org/lkml/2013/5/10/537 > > > > > > The schedule_user() was traced, and the preempt_enable_no_trace() that > > > the function tracer does caused for a schedule to occur. As the > > > scheduler uses rcu, and it was called before schedule_user() could tell > > > the kernel that the context is changing from user to kernel. > > > > That patch doesn't help unfortunatly. > > > > Dave, > > Can you send me your full .config, and also what you did to trigger > this? As I see ftrace_call is there, I'm assuming you have function > tracing enabled somewhere. Probably via perf, as ftrace_ops_control_func > is used by perf. > > Also, if you added anything special on the kernel command line, that > info will be useful too.
.config: http://paste.fedoraproject.org/14281/94052971/raw/
trace shows the problem process was 'cc1', so I was likely building a kernel at the time. There was also a trinity run going on in the background.
cmdline: nothing special..
BOOT_IMAGE=/vmlinuz-3.10.0-rc2+ root=UUID=bee21cd9-1852-4d1d-9e9d-2e44332b8df1 ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 consoleblank=0 console=ttyUSB0,115200 console=tty0 pause_on_oops=30 audit=0
Dave
| |