Here's a patch to dump error info (if we're actually getting an error)
from the i915 interrupt handler. The dump albert provided should also
help (looking at it now).
** Attachment added: "Output some error state at error interrupt time"
http://launchpadlibrarian.net/25683426/i915-error-info.p
Here's an updated one that will dump more info.
** Attachment added: "Updated debug patch"
http://launchpadlibrarian.net/25685701/i915-error-info-2.patch
--
[i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392
You received this bug notification because you are a membe
FWIW, on my T61 stock Jaunty Beta worked fine. I couldn't reproduce a
hang until I did a suspend/resume, which would usually die shortly after
resuming (nothing special needed). Even after updating things seem ok.
However with a 2.6.30ish kernel (from the drm-intel-next branch) things
hang very
Leann, I was seeing the same thing (hard lockup at login) with
2.6.30-rc2 from the drm-intel-next branch with my patch applied. It
could be due to my patch or some other interaction with more recent
kernels. I'm trying to reproduce the problem with 2.6.28 now (first the
Ubuntu kernel then one wit
I still haven't been able to reproduce this. I did notice that Albert,
Dustin and Bryce's intel_gpu_dump output was identical though (all had
what looked like i965 render commands in them). Some people have
reported that using EXA greedy migration made the bug go away, I wonder
if disabling rende
@Albert
Assuming you're seeing the same root problem that vindicates the 965 render
acceleration code.
--
[i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@Bryce
Your last hang is right after a render accel request again (the GPU dump
indicates that), but the interrupt state and such look ok:
Interrupt enable:00020053 <- user interrupts are on, which is good since we
use those to wait for requests to complete
Interrupt identity: <- no
Here's an alternate error state patch (the interrupt one I sent earlier
still needs work). It should add an i915_error_state file to debugfs,
which can be capture at hang time along with the rest of the files in
that directory.
** Attachment added: "Add error state to debugfs"
http://launchpad
> Attached are the results with Jesse's error state patch.
> After the freeze i915_gem_interrupt did not change.
>
> ** Attachment added: "gpudump-errorstate.tar.gz"
>http://launchpadlibrarian.net/25802051/gpudump-errorstate.tar.gz
Ok, so you got an instruction parser error, which indicates w
On Tue, 21 Apr 2009 14:45:09 -
Albert Damen wrote:
> > Can you try running your environment under INTEL_DEBUG=batch to see
> > batchbuffers as they're executed?
>
> I started gdm with sudo INTEL_DEBUG=batch /etc.init.d/gdm start and
> took the last 5.000 lines from the gdm log (gdm-tail.log)
On Tue, 21 Apr 2009 14:45:09 -
Albert Damen wrote:
> > Can you try running your environment under INTEL_DEBUG=batch to see
> > batchbuffers as they're executed?
>
> I started gdm with sudo INTEL_DEBUG=batch /etc.init.d/gdm start and
> took the last 5.000 lines from the gdm log (gdm-tail.log)
The "screen suddenly goes blank" issue and the underruns are probably
related, since the pipe will eventually just stop sending data if it
gets too many underruns. This looks very similar to the issue in
upstream https://bugs.freedesktop.org/show_bug.cgi?id=19304, there's a
patch available for te
Do you have the "xrandr" tool installed? If so, what does it report?
(Just open a terminal and run it.)
S-Video and TV out in general should be supported on Intel platforms...
--
[i945GM] S-Video output
https://bugs.launchpad.net/bugs/311090
You received this bug notification because you are a
Parameter 6 is probably I915_PARAM_NUM_FENCES_AVAIL, which is only part
of 2.6.29+ kernels. The error is harmless though; the driver should
fall back gracefully. Likewise, parameter 4 is
I915_SETPARAM_NUM_USED_FENCES, the other half of the new fence
management code.
The driver used to check drm
Marking "invalid" because this isn't really a bug, just a informational
message (though yes we could probably make it a little less scary :).
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged => Invalid
--
*ERROR* Unknown parameter 6
https://bugs.launchpad.net/bugs/353049
Y
FYI triplebuffer and page flipping options have been removed in later
versions of the driver. The implementation was broken by design (I'm
reworking it as part of fdo #20664).
--
[i965] X freezes when TripleBuffer On after resume
https://bugs.launchpad.net/bugs/331596
You received this bug notif
16 matches
Mail list logo
