Re: [Intel-gfx] Regression: Screen goes black on KMS

On Fri, 4 Nov 2011 23:28:07 +0100, Cedric Sodhi wrote: Non-text part: multipart/mixed > Hello, > > between 3.1 and cc03bbf1 on linux-next there has been a regression which > causes the screen to go black (not blank, backlight is still lit) on > KMS. The system runs fine in the background and, to

Re: [Intel-gfx] [PATCH v5] drm/i915: pass ELD to HDMI/DP audio driver

On 11/2/11 2:45 AM, Wu Fengguang wrote: Hi Christopher, The log does confirm that the drm_edid_to_eld function is running, and that we're not far from a solution: [ 21.061417] [drm:drm_edid_to_eld], ELD monitor TX-SR607 [ 21.061421] [drm:drm_edid_to_eld], ELD size 13, SAD count 8 It looks

[Intel-gfx] [PATCH] [RFC] drm/i915: Warning when reads or writes are dropped

The GTFIFODBG register gives us 3 error types when the fifo is accessed and full. Whenever we do a forcewake_put we can check this register to see if any of the CPU related errors occurred. Of more interest is perhaps the bit I am not checking which tells when some other part of the chip makes a r

Re: [Intel-gfx] "Invalid object handle" messages

On Sat, 5 Nov 2011 00:51:59 +0100, Clemens Eisserer wrote: > Hi, > > While I was trying out intel-git as well as mesa-i915git on my i945GM > based laptop I saw a few of the following messages in syslog: > > [ 3045.237121] [drm:i915_gem_do_execbuffer] *ERROR* Invalid object > handle 83886080 at

[Intel-gfx] "Invalid object handle" messages

Hi, While I was trying out intel-git as well as mesa-i915git on my i945GM based laptop I saw a few of the following messages in syslog: [ 3045.237121] [drm:i915_gem_do_execbuffer] *ERROR* Invalid object handle 83886080 at index 0 Any idea where they could come from, and what I can do to investig

[Intel-gfx] Regression: Screen goes black on KMS

27;ll try to bisect the problem as soon as I can. thank you --- /dev/fd/63 2011-11-04 23:01:22.080004826 +0100 +++ /dev/fd/62 2011-11-04 23:01:22.080004826 +0100 @@ -1,5 +1,5 @@ -] Linux version 3.1.0-next-2004 (root@slate) (gcc version 4.5.3 (Gentoo 4.5.3-r1 p1.0, pie-0.4.5) ) #1

Re: [Intel-gfx] [PATCH 3/3] [RFC] drm/i915: add interface to simulate gpu hangs

On Fri, Nov 4, 2011 at 14:31, Chris Wilson wrote: > On Fri, 4 Nov 2011 14:23:19 -0200, Eugeni Dodonov > wrote: > > Yep, it works for me. I can disable and enable rings at will by echo > [01] > > > /sys/kernel/debug/dri/0/i915_ring_stop > > > > I was using it for working further on that i915_erro

Re: [Intel-gfx] [PATCH 3/3] [RFC] drm/i915: add interface to simulate gpu hangs

On Fri, 4 Nov 2011 14:23:19 -0200, Eugeni Dodonov wrote: > Yep, it works for me. I can disable and enable rings at will by echo [01] > > /sys/kernel/debug/dri/0/i915_ring_stop > > I was using it for working further on that i915_error_state heuristics > idea, outside of intel_decode. It is *very*

Re: [Intel-gfx] [PATCH 3/3] [RFC] drm/i915: add interface to simulate gpu hangs

On Thu, Nov 3, 2011 at 14:10, Daniel Vetter wrote: > On Thu, Nov 03, 2011 at 01:56:11PM -0200, Eugeni Dodonov wrote: > > Could be handy for debugging, I like it. > > Have you tried actually blowing up your gpu with it? That's where the fun > starts ;-) My gpu-hanger branch contains the latest ite

Re: [Intel-gfx] [PATCH] drm/i915: enable cacheable objects on Ivybridge

On Thu, Nov 3, 2011 at 19:15, Jesse Barnes wrote: > IVB supports these bits as well. > > Signed-off-by: Jesse Barnes > Reviewed-by: Eugeni Dodonov -- Eugeni Dodonov ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop

Re: [Intel-gfx] [PATCH 2/5] drm: add an fb creation ioctl that takes a pixel format

On Fri, 04 Nov 2011 16:34:22 +0900 Joonyoung Shim wrote: > > + case V4L2_PIX_FMT_RGB24: > > + *depth = 24; > > + *bpp = 24; > > + break; > > In the depth = 24 and bpp = 32 case also the pixed_format is > V4L2_PIX_FMT_RGB24, but above function cannot detect it.

Re: [Intel-gfx] [PATCH 1/5] drm: add plane support

On Fri, 04 Nov 2011 11:22:10 +0900 Joonyoung Shim wrote: > > +struct drm_plane { > > + struct drm_device *dev; > > + struct device kdev; > > + struct device_attribute *attr; > > + struct list_head head; > > + > > + struct drm_mode_object base; > > + > > + uint32_t possible_crtcs; > > +

[Intel-gfx] Setting proper video mode

Hello! This is the diff between intel_reg_dumper output for iegd and xf86. Attached are full dumps. With iegd LVDS connected display is working, with xf86 only VGA is working. 19c19 VCLK_POST_DIV: 0x000200