linux-kernel - Re: [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output gets disabled/reenabled under load

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D3EC393.3010403@t-online.de>
Date:	Tue, 25 Jan 2011 13:35:31 +0100
From:	Knut Petersen <Knut_Petersen@...nline.de>
To:	Chris Wilson <chris@...is-wilson.co.uk>
CC:	jesse.barnes@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output
 gets disabled/reenabled under load

Am 25.01.2011 13:11, schrieb Chris Wilson:
>
>> LOG-2.6.38-rc2 is different. The kernel is a pure kernel 2.6.38-rc2 with one
>> exception: I changed  DRM_OUTPUT_POLL_PERIOD  to 3*HZ to increase
>> error probability.
>>
>> At log time [  678.598641]  you can see the status change of the VGA-2
>> connector (there is no physical VGA-2 connector on that mobo).
>>     
> I'm interested in knowing where the extra VGA-2 comes from. The only
> thing that comes to mind is a secondary function on the SDVO and knowing
> why that is unstable. Can you attach the complete drm.debug logs for
> 2.6.36 and 2.6.38 so I can see the initialisation order of the connectors.
>
>   

Attached find the startup logs. Both debuglevel 0xf.

Knut

View attachment "2.6.36.3.startup" of type "text/plain" (80253 bytes)

View attachment "2.6.38-rc2.startup" of type "text/plain" (96434 bytes)