On Fri, May 24, 2013 at 03:23:40PM -0400, Steven Rostedt wrote:
> On Fri, 2013-05-24 at 10:23 -0400, Dave Jones wrote:
>
> > .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
> >
>
> OK, I'm able to reproduce this. Looks like the same issue happens from
> other ways from userspace into the kernel (the next way was tracing
> system calls).
>
> Forget the other patch. Here's a new patch that is more specific to
> tracing and context tracking.
>
> Can you try this one out, please.
It's looking good so far.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
