On Fri, Sep 25, 2015 at 3:13 PM, Jiri Kosina <ji...@kernel.org> wrote: > On Fri, 25 Sep 2015, Sedat Dilek wrote: > >> > The sequence looks correct. So I don't really see what call sequence could >> > lead to calling flush_work() from __cancel_work_timer() with IRQs >> > disabled (which is what your stacktrace is suggesting). >> > >> > The fact that this doesn't happen with GCC-compiled kernels is really >> > suspicious. >> > >> >> Hm, and now? > > I guess one of the things to try is to generate ftrace graph trace to see > what exact function sequence leads to this warning. >
Can I do this via kernel-boot-parameter? No experiences with ftrace here. - Sedat - -- 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/
