public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: intel-gfx@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	David Airlie <airlied@linux.ie>
Subject: Linux 3.16-rc1: drm:intel_dp_start_link_train *ERROR* too many full retries, give up
Date: Mon, 16 Jun 2014 22:08:15 +0200	[thread overview]
Message-ID: <539F4EAF.5040209@hartkopp.net> (raw)

Hey all,

with my Debian unstable the upgrade from 3.15 to 3.16-rc1 failed with this fancy
[drm:intel_dp_start_link_train *ERROR* too many full retries, give up] message loop.

lightdm/XFCE4 doesn't start anymore (it tries several times but fails always).

Hm - I just found this stuff in my stock Debian Kernel too:
3.14-1-686-pae #1 SMP Debian 3.14.5-1 (2014-06-05) i686 GNU/Linux


[    6.461232] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[    6.873772] dell_wmi: Received unknown WMI event (0x11)
[    6.884336] Console: switching to colour frame buffer device 240x67
[    6.948511] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    6.948513] i915 0000:00:02.0: registered panic notifier

[    7.430429] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

But at least it starts with the 3.14 (any the latest 3.15).

I have a Intel(R) Core(TM) i7 CPU M 640  @ 2.80GHz with Intel HD graphics.

Any idea?

Regards,
Oliver

             reply	other threads:[~2014-06-16 20:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 20:08 Oliver Hartkopp [this message]
2014-06-16 21:47 ` Linux 3.16-rc1: drm:intel_dp_start_link_train *ERROR* too many full retries, give up Daniel Vetter
2014-06-17 18:38   ` Oliver Hartkopp
2014-06-28 16:41     ` Oliver Hartkopp
2014-06-30  8:57       ` Jani Nikula
2014-06-30 17:42         ` Oliver Hartkopp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=539F4EAF.5040209@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox