[snip] what is the reason for the corrupt page tables? Urm... pass on that one ;)
Jamie? Does the page table look the same before suspend? (Or when the bug is not showing?) Since the page-table can be acccessed via mapped memory in the video- card's memory/IO/register space, it seems possible that an errant 3D instruction / other GPU command could actually trample it. Or.. (perhaps more likely), it could be the allocator routines in the driver / DRI manager / "AGP" driver etc.. As far as I could tell, the entries are removed and re-added after suspend / resume, so it doesn't seem like it would be the BIOS's fault for messing them up.. however if the BIOS is bad, and executes SMI code on some system event, it does have the ability to trample pretty much anything. I have 945GM and don't see this bug, haven't been able to reproduce it (even trying to force the exact same resolution, reproduction steps etc..). Which does somewhat suggest that the bug is at least triggered by something not common to all machines showing this bug. This Intel driver guys know about this bug, and hopefully they will have better insight as to the cause. I've passed along the useful information from the page-table dumping (and a link to this bug). -- screen artifacts after resume, part row of pixels in error (945GM) https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
