Re: tracing ring_buffer_resize oops.

[Steven Rostedt <rostedt@xxxxxxxxxxx>]

On Thu, 2012-05-24 at 17:15 -0400, Dave Jones wrote:
> On Thu, May 24, 2012 at 04:33:06PM -0400, Steven Rostedt wrote:
> 
>  > I'm kicking off the ktest that initially caused this issue hoping that
>  > it reproduces the bad tree again.
>  > 
>  > BTW, did you happen to upgrade gcc or anything? The ktest I run does
>  > test against different gcc's and I don't think I had it do a make clean
>  > between the switch. That may be the cause of this problem too :-?
> 
> No gcc updates. It's a Fedora 17 box, so there's been hardly any updates this
> last week or so as things have been frozen leading into the release.
> 

I'm currently running a ktest that is similar to what I think I ran when
the bug hit (I didn't save off the config file :-(  )

But it looks like it did do a mrproper between switching gcc's so I no
longer think that was the issue.

Thanks,

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html