On Tue, 8 Sep 2009 15:06:21 -0700 (PDT) Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > > 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. No excuses. This is a serious bug; I just don't want to paper over it. > 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. Yeah sorry, this is the first I've seen of it... I usually troll the regressions lists but I must have missed this one. > 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. Sure, looking at it now. -- Jesse Barnes, Intel Open Source Technology Center -- 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
