Upstream thinks this is fixed in newer kernels, so marking it as such.
If you can reproduce on natty, please file a new bug.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which
** Changed in: xserver-xorg-video-intel
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/560376
Title:
[i945gm] Random X hang
** Changed in: xserver-xorg-video-intel
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/560376
Title:
[i945gm] Random X hang
This seems very similar to the bug I'm experiencing, on an Asus Eee PC
1000HE, with 945GME.
I can get out of it with magic SysRq R-E.
If it is, in fact, the same, we can at least drop the amd64 tag.
[ 9960.352098] INFO: task i915:246 blocked for more than 120 seconds.
[ 9960.352110] echo 0
If it is, in fact, the same, we can at least drop the amd64 tag.
I haven't yet seen a graphics related bug where i386 or amd64 has made
a difference, so by default we assume that it affects both
architectures. The best reason to have the tag there as far as I can
see is that it makes it easy to
I haven't seen this in a while. If I don't see it in the next week,
I'll close this.
Nope, that was just a lucky 10 days. Still present in lucid.
--
[i945gm] Random X hang
https://bugs.launchpad.net/bugs/560376
You received this bug notification because you are a member of Ubuntu-X,
which is
I haven't seen this in a while. If I don't see it in the next week, I'll
close this.
--
[i945gm] Random X hang
https://bugs.launchpad.net/bugs/560376
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
Thank you for the updated dump. It seems that intel_gpu_dump output and
i915_error_state is still incompatible, but at least now we know that
this is not due to the limited debugging capability of the ubuntu
kernel. Maybe this tells the developers something useful.
I have forwarded your bug
The debug output with 2.6.32 (Lucid) kernels isn't very reliable anyway.
Could you try the 2.6.34-rc3 mainline kernel and capture dmesg and
i915_error_state with that? If you can also add drm.debug=0x02 as a kernel
parameter, that would make dmesg output more verbose with respect to this
kind
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Confirmed
--
[i945gm] Random X hang
https://bugs.launchpad.net/bugs/560376
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
** Tags added: freeze
--
[i945gm] Random X hang
https://bugs.launchpad.net/bugs/560376
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
___
Mailing list:
Hmm... i915_error_state and intel_gpu_dump output don't seem to be
compatible (different EIR, PGTBL_ER and ACTHD) which may be because they
are captured at different times or have something to do with the
intel_gpu_dump error message in dmesg output.
The debug output with 2.6.32 (Lucid) kernels
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43731093/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/43731094/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43731095/Dependencies.txt
**
i915_error_state:
Time: 1270717090 s 854796 us
EIR: 0x0010
PGTBL_ER: 0x0102
INSTPM: 0x
IPEIR: 0x
IPEHR: 0x
INSTDONE: 0x7fc0
ACTHD: 0x
** Attachment added: dri_debug.tgz
http://launchpadlibrarian.net/43731656/dri_debug.tgz
**
14 matches
Mail list logo
