On Wed, 12 Nov 2008, Pekka Paalanen wrote: > On Mon, 10 Nov 2008 22:18:19 -0500 (EST) > Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > > > > Pekka, > > > > I forgot to add you to the Cc list. Could you test this patch to see if it > > fixes the bug you reported. It fixed a bug I was able to reproduce, but I > > was never able to reproduce the exact same bug you have seen. > > Thanks, Steve. > > I didn't have time to try it myself yet, but a kind soul tried it for me. > He used 2.6.28-rc4 and was immediately able to trigger the bug by just: > cd /debug/tracing > echo 0 > tracing_enabled > echo 200 > trace_entries > > Then he applied the patch you referred to, and the bug is still present. > He has a 32-bit x86 amd system, and I'm on x86_64. > > I don't know why you couldn't reproduce it, maybe you have all the tracers > enabled in the kernel config, when we only have MMIOTRACE. > > I can't promise to look into this deeper in the near future :-/ > OK, I'll disable everything but MMIOTRACE and see if I can reproduce it. Thanks, -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
