On Wed, 12 Feb 2014, Vince Weaver wrote: > On Tue, 11 Feb 2014, Peter Zijlstra wrote: > > > > I'll see if I can run through the reproduction case by hand. > > I've come up with an even simpler test case with all of the extraneous > settings removed. Included below. > > It is triggered in this case when you have: > > An event group of breakpoint, cycles, branches > An event of instructions with precise=1 > A tracepoint > > and then you close the tracepoint.
and for what it's worth, it's the cycles event (type=0 config=0) that's causing the WARN_ON. It looks like I'm going to have to resort to sprinkling the code with printk()s to solve this one. Vince -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
