On Tue, 8 Sep 2009, Jesse Barnes wrote: > > Yeah, saw that. I don't think that's the root cause though. If we see > a user interrupt after gem_idle is called we may have serious issues in > our command handling code. Quite frankly, I do not understand why you seem to be making excuses for code that causes a very nasty and undebuggable oops, causing the machine to die. This regression is almost two months old, and apparently the Intel graphics people DID ABSOLUTELY NOTHING about it during those two months, because they couldn't be bothered to look at it. And now, when I pinpointed exactly where the oops happens, and what the cause is, you seem to be trying to hold things up. I wanted to do the final 2.6.31 release yesterday, quite frankly I'm not in the _least_ interested in excuses, I'm interested in something that at least gets us back to the 2.6.30 state that doesn't oops! Get me a patch, please. If disabling the interrupts early won't work, get me something else. Stop delaying it - it's been pending for 48 days already. Linus -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
