[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <0d30dc$ktil71@orsmga001.jf.intel.com>
Date: Sun, 30 Jan 2011 12:25:08 +0000
From: Chris Wilson <chris@...is-wilson.co.uk>
To: Nico Schottelius <nico-kernel-20110117@...ottelius.org>
Cc: Nico Schottelius <nico-kernel-20110117@...ottelius.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: More display errors in 2.6.38-rc2-00175-g6fb1b30 (was 2.6.38-rc2-00175-g6fb1b30)
On Sun, 30 Jan 2011 13:08:53 +0100, Nico Schottelius <nico-kernel-20110117@...ottelius.org> wrote:
> [10627.321357] i915 0000:00:02.0: power state changed by ACPI to D0
> [10627.321363] i915 0000:00:02.0: power state changed by ACPI to D0
> [10627.321369] i915 0000:00:02.0: setting latency timer to 64
> [10627.322724] sd 0:0:0:0: [sda] Starting disk
> [10627.345649] intel ips 0000:00:1f.6: MCP limit exceeded: Avg temp 20425, limit 9000
> [10627.516702] [drm:ironlake_fdi_link_train] *ERROR* FDI train 1 fail!
> [10627.516862] [drm:ironlake_fdi_link_train] *ERROR* FDI train 2 fail!
> [10627.535575] usb 1-1.3: reset full speed USB device using ehci_hcd and address 3
> [10627.570055] [drm:ironlake_fdi_link_train] *ERROR* FDI train 1 fail!
> [10627.570215] [drm:ironlake_fdi_link_train] *ERROR* FDI train 2 fail!
So upon resume we fail to setup the connection between the CPU and PCH,
which would cause a broken display.
Now we haven't directly modified the FDI training in the .38 cycle, but we
have tweaked and enabled various power saving features for Ironlake that
have proven to be unstable in the past. (Hence why we had to disable them
but the obvious problems had been fixed...)
This should hopefully find the culprit:
$ git bisect start drivers/gpu/drm/i915/intel_display.c
$ git bisect good v2.6.37
$ git bisect bad
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists