This bug report was marked as Triaged a while ago but has not had any
updated comments for quite some time. Please let us know if this issue
remains in the current Ubuntu release,
http://www.ubuntu.com/getubuntu/download . If the issue remains, click
on the current status under the Status column
Have not seen this lockup with the lucid kernel. Marking as resolved.
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
You received this bug notification because you are a member of
Just hit this bug again (huh, had a good run). Is this suitable for
backporting to the karmic kernel?
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for
** Tags added: xorg-needs-kernel-fix
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
You received this bug notification because
The patch noted in comment #3 and #4 is now upstream in linus' tree.
This patch however is not in the Karmic kernel tree.
ogasaw...@yoji:~/linux-2.6$ git show 0ef82af7253c1929a3995f271b8b0db462d1a0c3
commit 0ef82af7253c1929a3995f271b8b0db462d1a0c3
Author: Chris Wilson ch...@chris-wilson.co.uk
I'm still seeing GPU lockups with this hardware on the current kernel -
how would I know if they're the same lockup?
I had a lockup this morning which I reported as a new bug (bug #445719);
I guess if I'm reading the intel_gpu_dump.txt right for that one, then
it's not a problem of the ringbuffer
Ok, looking back at the original intel_gpu_dump.txt file for this bug, I
understand now what I'm supposed to be looking for (sorry, had another
dri_debug directory here locally with the same datestamp that I was
looking at, which didn't show this error). It doesn't appear that I've
seen this
As per comment #3 this is sounding like a kernel bug, so re-filing. The
upstream bug was closed as expired but believed fixed - are you able to
reproduce this with current karmic bits?
** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
** Changed in: xserver-xorg-video-intel
Status: Confirmed = Fix Released
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=22336
Importance: Unknown
Status: Unknown
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
You received this bug notification because you are a member
** Changed in: xserver-xorg-video-intel
Status: Unknown = Confirmed
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
fwiw the fix Albert mentions is an attachment on
https://bugs.freedesktop.org/show_bug.cgi?id=22336
** Bug watch added: freedesktop.org Bugzilla #22336
https://bugs.freedesktop.org/show_bug.cgi?id=22336
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
This issue was discussed on intel-gfx recently. The ringbuffer wraps
around in the middle of an instruction:
0x0001fff8: 0x1081: MI_STORE_DATA_INDEX
0x0001fffc: 0x0080:dword 1
Buffer size too small in MI_STORE_DATA_INDEX (2 3)
A fix has been committed in Eric Anholt's
** Summary changed:
- GPU lockup with intel 2:2.8.1-1ubuntu1 on i945GM
+ [i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
** Tags added: 945gm freeze karmic
--
[i945GM] GPU lockup with intel 2:2.8.1-1ubuntu1
https://bugs.launchpad.net/bugs/424613
You received this bug notification because you
14 matches
Mail list logo
