Florian Westphal <fw@xxxxxxxxx> wrote: > > Strange. Can you completely revert 2d72afb340657f03f7261e9243b44457a9228ac7 > > and then apply this patch instead? > > Any news? For some reason, I can no longer reproduce the problem in new kernels that I build. I can still reproduce it in the kernels that I built last week. But if I build a new one, from the same commit as I was able to reproduce it from before, the new kernel build can't reproduce it. I didn't change anything (like compiler version) since. So I'm stumped. I'm not sure what this means, other than that I can't test any new patches because any new build I do doesn't exhibit the problem. I guess at this point I can't rule out some kind of hardware failure on my end (though that would seem very strange that it would consistently point to a specific commit, and the problem went away after reverting, if it was a hardware problem). So maybe we can ignore this for now and see if it comes up again with anyone else. Cheers, -- Dan
