From: Chris Wilson <chris@chris-wilson.co.uk>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: xrandr "DP2 unknown connection"
Date: Sat, 23 Oct 2010 11:05:11 +0100 [thread overview]
Message-ID: <5b55a1$ierq76@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1287827993.5454.9.camel@zwerg>
On Sat, 23 Oct 2010 11:59:53 +0200, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> Am Samstag, den 23.10.2010, 10:40 +0100 schrieb Chris Wilson:
> > Which does not seem likely given that we only fail intel_dp_init for the
> > memory allocation failure at the start. Some other form of memory
> > corruption or bogosity?
>
> Tools to use? memtest86? memory_corruption_check_size=?
The starting point would be to add drm.debug=0xf to your boot line and
lets have a close look at what is going on during boot + discovery [dmesg].
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-10-23 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 8:09 xrandr "DP2 unknown connection" Alexey Fisher
2010-10-23 9:34 ` Chris Wilson
2010-10-23 9:40 ` Chris Wilson
2010-10-23 9:59 ` Alexey Fisher
2010-10-23 10:05 ` Chris Wilson [this message]
[not found] ` <1287830095.5237.0.camel@zwerg>
[not found] ` <B32E3D5F1713054290B4FF257B89C51A292F25BBC6@shsmsx502.ccr.corp.intel.com>
2010-10-25 6:39 ` Alexey Fisher
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='5b55a1$ierq76@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=bug-track@fisher-privat.net \
--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