linux-kernel - Re: [3.5 regression] DRM: Massive (EDID-probing?) X startup delay on ATI Radeon RV770 (HD4870)

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: <CADnq5_O3agchGGGGX0Ozei9F4SMsM+mMRfw=F03Ux8QzZd4CQA@mail.gmail.com>
Date:	Mon, 6 Aug 2012 09:42:03 -0400
From:	Alex Deucher <alexdeucher@...il.com>
To:	Nix <nix@...eri.org.uk>
Cc:	linux-kernel@...r.kernel.org, Jerome Glisse <j.glisse@...il.com>,
	alex.deucher@...il.com
Subject: Re: [3.5 regression] DRM: Massive (EDID-probing?) X startup delay on
 ATI Radeon RV770 (HD4870)

On Sat, Aug 4, 2012 at 12:13 PM, Nix <nix@...eri.org.uk> wrote:
> Possibly-relevant info:
>
>  - Two DVI monitors, identical specs, one dual-head graphics card
>    (so no VGA switcheroo or awesome-yet-terrifying PRIME madness needed)
>
>  - KMS, Xserver 1.12.3, driver 6.14.6-28 (trunk current as of today),
>    Mesa 8.0.4, libdrm 2.4.37
>
> As of kernel 3.5 EDID probing of the older of my two monitors appears to
> have subtly broken. The log shows that it appears to work -- KMS comes
> up OK and I get a working console -- but then X stops during startup for
> nearly a minute (with both monitors black) before coming back to life
> again and EDID-probing the monitor a further six times for no obvious
> reason. (Full log attached, and xorg.conf, for what little use it is.)
>
> Something appears to be wrong, but I have no idea what. I've not changed
> anything other than the kernel since my last non-huge-delayed startup
> earlier this week, and both the monitors still work, including the one
> suffering a huge startup delay.

Can you bisect the kernel or profile Xorg and see what's causing it?
There haven't been any i2c changes in the radeon kernel driver in a
while.  I'm assuming it's only the kernel that you changed?  E.g.,
just to be sure, does booting a different kernel with the same
userspace components work correctly?

Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/