* xrandr "DP2 unknown connection"
@ 2010-10-23 8:09 Alexey Fisher
2010-10-23 9:34 ` Chris Wilson
0 siblings, 1 reply; 6+ messages in thread
From: Alexey Fisher @ 2010-10-23 8:09 UTC (permalink / raw)
To: intel-gfx
Hi,
xrandr report me new connection i never seen before
"DP2 unknown connection". There is only DVI monitor attached to this
board. kernel 2.6.36-rc8-01148-g3c17fe4 from intel_drm_next
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis)
521mm x 293mm
1920x1080 60.0*+
1680x1050 60.0
1280x1024 75.0 60.0
1440x900 75.0 59.9
1280x960 60.0
1152x864 75.0
1024x768 75.1 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 72.8 75.0 66.7 60.0
720x400 70.1
DP2 unknown connection (normal left inverted right x axis y axis)
1360x768 59.8
1152x864 60.0
1024x768 60.0
800x600 60.3
640x480 59.9
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xrandr "DP2 unknown connection"
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
0 siblings, 1 reply; 6+ messages in thread
From: Chris Wilson @ 2010-10-23 9:34 UTC (permalink / raw)
To: Alexey Fisher, intel-gfx
On Sat, 23 Oct 2010 10:09:57 +0200, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> Hi,
> xrandr report me new connection i never seen before
> "DP2 unknown connection". There is only DVI monitor attached to this
> board. kernel 2.6.36-rc8-01148-g3c17fe4 from intel_drm_next
So unknown connection is only reported for DP if the structure does not
match one of the known registers. Sounds like we bailed during
initialisation, but after hooking the structure into the drm connector
list.
--
Chris Wilson, Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xrandr "DP2 unknown connection"
2010-10-23 9:34 ` Chris Wilson
@ 2010-10-23 9:40 ` Chris Wilson
2010-10-23 9:59 ` Alexey Fisher
0 siblings, 1 reply; 6+ messages in thread
From: Chris Wilson @ 2010-10-23 9:40 UTC (permalink / raw)
To: Alexey Fisher, intel-gfx
On Sat, 23 Oct 2010 10:34:38 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Sat, 23 Oct 2010 10:09:57 +0200, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> > Hi,
> > xrandr report me new connection i never seen before
> > "DP2 unknown connection". There is only DVI monitor attached to this
> > board. kernel 2.6.36-rc8-01148-g3c17fe4 from intel_drm_next
>
> So unknown connection is only reported for DP if the structure does not
> match one of the known registers. Sounds like we bailed during
> initialisation, but after hooking the structure into the drm connector
> list.
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?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xrandr "DP2 unknown connection"
2010-10-23 9:40 ` Chris Wilson
@ 2010-10-23 9:59 ` Alexey Fisher
2010-10-23 10:05 ` Chris Wilson
0 siblings, 1 reply; 6+ messages in thread
From: Alexey Fisher @ 2010-10-23 9:59 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
Am Samstag, den 23.10.2010, 10:40 +0100 schrieb Chris Wilson:
> On Sat, 23 Oct 2010 10:34:38 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > On Sat, 23 Oct 2010 10:09:57 +0200, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> > > Hi,
> > > xrandr report me new connection i never seen before
> > > "DP2 unknown connection". There is only DVI monitor attached to this
> > > board. kernel 2.6.36-rc8-01148-g3c17fe4 from intel_drm_next
> >
> > So unknown connection is only reported for DP if the structure does not
> > match one of the known registers. Sounds like we bailed during
> > initialisation, but after hooking the structure into the drm connector
> > list.
>
> 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=?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xrandr "DP2 unknown connection"
2010-10-23 9:59 ` Alexey Fisher
@ 2010-10-23 10:05 ` Chris Wilson
[not found] ` <1287830095.5237.0.camel@zwerg>
0 siblings, 1 reply; 6+ messages in thread
From: Chris Wilson @ 2010-10-23 10:05 UTC (permalink / raw)
To: Alexey Fisher; +Cc: intel-gfx
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: xrandr "DP2 unknown connection"
[not found] ` <B32E3D5F1713054290B4FF257B89C51A292F25BBC6@shsmsx502.ccr.corp.intel.com>
@ 2010-10-25 6:39 ` Alexey Fisher
0 siblings, 0 replies; 6+ messages in thread
From: Alexey Fisher @ 2010-10-25 6:39 UTC (permalink / raw)
To: Jin, Gordon, Chris Wilson; +Cc: intel-gfx
Am Montag, den 25.10.2010, 08:40 +0800 schrieb Jin, Gordon:
> Alexey Fisher wrote on Saturday, October 23, 2010 6:35 PM:
> > Am Samstag, den 23.10.2010, 11:05 +0100 schrieb Chris Wilson:
> >> 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].
> >
> > Here is huge dmesg
>
> The attachment is so big that has been blocked by the mailing list.
>
> I'd suggest you put it into a bug report according to http://www.intellinuxgraphics.org/how_to_report_bug.html, and reply the email with bug link.
>
> Thanks
> Gordon (serving as intel-gfx@ administrator)
Here is the bugreport:
https://bugs.freedesktop.org/show_bug.cgi?id=31094
Regards,
Alexey
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-10-25 6:39 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
[not found] ` <1287830095.5237.0.camel@zwerg>
[not found] ` <B32E3D5F1713054290B4FF257B89C51A292F25BBC6@shsmsx502.ccr.corp.intel.com>
2010-10-25 6:39 ` Alexey Fisher
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox