[Ubuntu-x-swat] [Bug 644680] Re: [arrandale] GPU lockup 8a64be8b (IPEHR: 0x01800002)

2012-07-23 Thread Bryce Harrington
*** This bug is a duplicate of bug 1023691 *** https://bugs.launchpad.net/bugs/1023691 ** This bug is no longer a duplicate of bug 645057 [arrandale] GPU lockup (IPEHR: 0x0182) ** This bug has been marked a duplicate of bug 1023691 [arrandale] False GPU lockup IPEHR: 0x0182 --

[Ubuntu-x-swat] [Bug 644680] Re: [arrandale] GPU lockup 8a64be8b (IPEHR: 0x01800002)

2011-01-18 Thread Bryce Harrington
*** This bug is a duplicate of bug 645057 *** https://bugs.launchpad.net/bugs/645057 ** This bug has been marked a duplicate of bug 645057 [arrandale] GPU lockup (IPEHR: 0x0182) * You can subscribe to bug 645057 by following this link: https://bugs.launchpad.net/ubuntu/+source/xserver

[Ubuntu-x-swat] [Bug 644680] Re: [arrandale] GPU lockup 8a64be8b (IPEHR: 0x01800002)

2010-10-06 Thread JasonH
Updates applied earlier in the week seem to have handled the situation. I did not disable the error report for this application, in order to recreate the scenario upon request. Unfortunately for this bug, less so for me, I cannot recreate at this time. -- [arrandale] GPU lockup 8a64be8b (IPEHR:

[Ubuntu-x-swat] [Bug 644680] Re: [arrandale] GPU lockup 8a64be8b

2010-10-06 Thread Robert Hooker
** Description changed: Binary package hint: xserver-xorg-video-intel Using the application crash handler to pass along the issue. I've not seen any ill effects aside from apport-gpu-error.intel.py is reported as getting closed unexpectedly. This bug was created using that popup.

[Ubuntu-x-swat] [Bug 644680] Re: [arrandale] GPU lockup 8a64be8b

2010-09-21 Thread JasonH
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/644680/+attachment/1619848/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/644680/+attachment/1619849/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http