On Thu, Mar 28, 2013 at 11:35 AM, Dirk Brandewie <dirk.brandewie@xxxxxxxxx> wrote: >>> pid_param_set() is on the stack which means that something is changing >>> the debugfs parameters or the stack is FUBAR. >>> >> I somehow doubt the stack is messed up as the call traces are always >> identical. >> (pid_param_set() seems to be in first trace as well.) >> > > I agree that the two oops are likely the same but unless something is > crawling > through debugfs writing random values to the files there pid_param_set() > should not be on any stack anywhere. Ok. > > There was a similar bug reported by fedora: > https://bugzilla.redhat.com/show_bug.cgi?id=920289 > > This bug has not showed up again since rc3 can you try the current rc to see > if > you still see the problem? > I updated the Fedora BZ - the oops I got is from latest git as of yesterday. So I think the bug is still there post -rc3. Parag -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
