Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756592Ab2HJRQm (ORCPT ); Fri, 10 Aug 2012 13:16:42 -0400 Received: from icebox.esperi.org.uk ([81.187.191.129]:36444 "EHLO mail.esperi.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751831Ab2HJRQi (ORCPT ); Fri, 10 Aug 2012 13:16:38 -0400 From: Nix To: Alex Deucher Cc: linux-kernel@vger.kernel.org, Jerome Glisse Subject: Re: [3.5 regression] DRM: Massive (EDID-probing?) X startup delay on ATI Radeon RV770 (HD4870) References: <878vdumy99.fsf@spindle.srvr.nix> Emacs: if it payed rent for disk space, you'd be rich. Date: Fri, 10 Aug 2012 18:16:35 +0100 In-Reply-To: (Alex Deucher's message of "Mon, 6 Aug 2012 09:42:03 -0400") Message-ID: <87r4re7jm4.fsf@spindle.srvr.nix> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-DCC-wuwien-Metrics: spindle 1290; Body=3 Fuz1=3 Fuz2=3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1625 Lines: 36 On 6 Aug 2012, Alex Deucher verbalised: > On Sat, Aug 4, 2012 at 12:13 PM, Nix 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.) False alarm. Well, the massive number of EDID probes is consistent, but that was present in earlier kernels too. The minute-long X start process was what was unusual, and intermittent: even in 3.5, it starts in a relatively 'normal' eight seconds normally. I suspect system load, or i2c bus timeouts or something (it is a really crap bus, after all). Anyway, it hasn't recurred, which makes it hard to track down further, let alone bisect :( I think we have to let this one rest. Dammit. I hate to let a bug slip away. -- NULL && (void) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/