[Bug 64764] 845G: crtc active state doesn't match with hw state

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=64764

--- Comment #14 from mlsemon35 at gmail.com ---
(In reply to comment #13)
> Can you please grab the latest intel-gpu-tools git from
> http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/ and then grab the
> output of intel_reg_dumper both while the screen is on and once it's off
> (i.e. after the WARN hit dmesg)?
> 
> If you don't have ssh to do grab the 2nd dump you can do
> 
> xset dpms force off ; sleep 2; intel_reg_dumper > reg_dump.off

It looks like I did not mention that the monitor comes back up, as if `xset
dpms force off` does only a temporary blanking of the screen, barely 2 seconds.

intel-gpu-tools-1.3 is part of slackware-current, so I used it, and it gave me
this (as root)...

root:~$ xset dpms force off; sleep 2; intel_reg_dumper > dumper.out
Gen2/3 Ranges are not supported. Please use unsafe access.Aborted

...which I saw last year when I compiled intel-gpu-tools from source and tried
to use it.

As for tools that might work here, there's a /sys/kernel/debug/dri directory
available, and the i915 tracers are available.  After I go back home tomorrow,
serial console/capture will be available as well.

This DRM debug and DPMS debugging is causing X11 to become unstartable
sometimes.  It acts like it's going to start Xfce but stops at a blank screen. 
When I switch back to the console from which I typed `startx`, this shows up
over and over:

__kgem_bo_map__gtt: failed to retrieve GTT offset for handle=26: 5

Is this a message from the Intel X11 driver?  Ctrl-c stops X11 and the printing
of these messages, but it takes a reboot in order to use X11 again.

Thanks for bearing with me!  [Reminder to self:  More coffee is needed in the
morning.]

Michael

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130523/8b16fe97/attachment.html>