Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753999Ab0FGGJt (ORCPT ); Mon, 7 Jun 2010 02:09:49 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:51550 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753395Ab0FGGJr convert rfc822-to-8bit (ORCPT ); Mon, 7 Jun 2010 02:09:47 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Q9bpOEyu9W7jnSHFQLArZ2El7D8s6WSJ4XCrulId6UA1tSmOlBJvABZPf6F2/kUeaO tLJ+bE8PIeY1tSyjKx3DMgv++OXfRTom5H/Gum5//BQnJPSQ0H/9IS6hq7RGps0CgI2M O5WBTBr2oZ44esr+SKQwPSA6n9XlhmnbO2+Zc= MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 7 Jun 2010 08:09:45 +0200 Message-ID: Subject: Re: Linux 2.6.35-rc2 From: Torsten Kaiser To: Alex Deucher Cc: Linus Torvalds , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2106 Lines: 48 On Mon, Jun 7, 2010 at 7:58 AM, Alex Deucher wrote: > On Sun, Jun 6, 2010 at 11:04 AM, Torsten Kaiser > wrote: >> [CC:Jeff+Tejun not removed, because you might want to look at the >> attached dmesgs] >> >> On Sun, Jun 6, 2010 at 4:19 PM, Linus Torvalds >> wrote: >>> On Sun, 6 Jun 2010, Torsten Kaiser wrote: >>>> >>>> The first problem that shows up is, that after the KMS switches to the >>>> correct video mode (1280x1024 for an DVI attached LCD), the display >>>> begins to flicker. Every 1..2 seconds (guesstimated) the display turns >>>> off and on again. Something in the new powersaving? >>> >>> Or maybe a borderline display timing that the display has trouble syncing >>> up with? >> >> With 2.6.34 and any previous KMS kernels the output was always stable. >> (I think, I switch to the radeon KMS on 2.6.32) >> The onscreen menu of the monitor showed 1280x1024@60.2Hz for >> 2.6.35-rc2, if I recall correctly. >> Now back on 2.6.34 its 1280x1024@59.9Hz. > > The pm code shouldn't have any affect as your system only has one > power state, so it never kicks in. ?It sounds like a display pll > problem, but there haven't been any changes to that code since 2.6.34. > ?Any chance you could bisect it? Not really. -rc1 did not boot for me (although if I disable v4l that might work), and there is this memory corruption error. Regarding the PLLs, did you see this mail? It contains the drm.debug=15 output from 2.6.34 and 2.6.35-rc2. http://lkml.org/lkml/2010/6/6/126 The debug output from radeon_set_pll looks identical. But in 2.6.35 a call to [drm:radeon_legacy_tmds_int_dpms], seems new. The switchoff intervall is ~10 seconds, not 1..2 as I guessed in the first mail. Any idea if there is something in the KMS code that triggers at this intervall? Torsten -- 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/