Bug#481345: My bug (484049) may be a duplicate of this
Sam, can you reproduce the bug, then SSH into the target machine and look for a block of text that mentions Error in I830WaitLpRing(), timeout for 2 seconds? I think this bug and my bug with scorched3d are related, but I'm not quite ready to mark mine as a duplicate yet. For what it's worth, the G965 seems to be upset because of an invalid command, most likely because either the intel driver or Mesa overwhelmed it and overran the ring buffer, sending the G965's command sequencer spinning off into space. I'll do more investigating tonight to see who the guilty party is. -lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481345: My bug (484049) may be a duplicate of this
Lee Cremeans wrote: Sam, can you reproduce the bug, then SSH into the target machine and look for a block of text that mentions Error in I830WaitLpRing(), timeout for 2 seconds? I think this bug and my bug with scorched3d are related, but I'm not quite ready to mark mine as a duplicate yet. It's very hard to know where such a bug comes from. The error in i830WaitLpRing is basically just a random GPU lockup which may be caused by multiple bugs in Mesa or in the video driver. I usually don't merge such bugs to avoid messing up their contents. We already have multiple bug reports like these actually. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
