From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Linux 3.16-rc1: drm:intel_dp_start_link_train *ERROR* too many full retries, give up
Date: Mon, 30 Jun 2014 19:42:17 +0200 [thread overview]
Message-ID: <53B1A179.4040605@hartkopp.net> (raw)
In-Reply-To: <87mwcuixlo.fsf@intel.com>
Hello Jani,
On 30.06.2014 10:57, Jani Nikula wrote:
> On Sat, 28 Jun 2014, Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>> The latest git pull from Linus' tree fixed my issue.
>>
>> vmlinuz-3.16.0-rc2-00211-gd7933ab (26.6. 21:19) was bad
>> vmlinuz-3.16.0-rc2-00319-g3e7b256 (28.6. 09:23) works again
>>
>> There are two pulls with 'drm-fixes' and 'x86/urgent' in this area.
>> Don't know what it was in detail - but it's fixed now (lightdm/xfce4 runs).
>
> Thanks for reporting back, I'm glad it works for you now.
>
> However, for closure, I would appreciate it if you could do a reverse
> bisect to find out which commit fixed things for you.
I checked the 'x86/urgent' patches which talk about some major glibc breakage
that have been fixed in that pull request. So I just reverted the patches form
the 'drm-fixes' to make sure that my problem was not introduced by the
i915/drm stuff.
It finally made do difference whether the last 'drm-fixes' where applied or
not. It obviously was the glibc issue for x32 which killed my lightdm/xfce4
startup.
Best regards,
Oliver
prev parent reply other threads:[~2014-06-30 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 20:08 Linux 3.16-rc1: drm:intel_dp_start_link_train *ERROR* too many full retries, give up Oliver Hartkopp
2014-06-16 21:47 ` 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 [this message]
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=53B1A179.4040605@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.