From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0! Date: Thu, 1 Oct 2015 14:13:09 +0300 Message-ID: <20151001111309.GA26517@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTP id 9FDCE6E09B for ; Thu, 1 Oct 2015 04:13:13 -0700 (PDT) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Jiri Kosina Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org List-Id: intel-gfx@lists.freedesktop.org T24gVGh1LCBPY3QgMDEsIDIwMTUgYXQgMTE6NDE6MzRBTSArMDIwMCwgSmlyaSBLb3NpbmEgd3Jv dGU6Cj4gSGksCj4gCj4gc2luY2UgSSd2ZSB1cGRhdGVkIG9uIG15IHRoaW5rcGFkIHgyMDBzIHRv IGxhdGVzdCBMaW51cycgdHJlZSAoMzIzNTAzMSksIEkgCj4gYW0gZ2V0dGluZyBhIGxvdCBvZgo+ IAo+IAlbZHJtOmRybV9jYWxjX3RpbWVzdGFtcGluZ19jb25zdGFudHMgW2RybV1dICpFUlJPUiog Y3J0YyAyMTogQ2FuJ3QgY2FsY3VsYXRlIGNvbnN0YW50cywgZG90Y2xvY2sgPSAwIQoKV2hhdCdz IGEgbG90PyBJIHRoaW5rIHlvdSBzaG91bGQgc2VlIGF0IG1vc3QgYSBmZXcgZHVyaW5nIGRyaXZl ciBsb2FkLAphbmQgbWF5YmUgcmVzdW1lLgoKSWYgeW91J3JlIHNlZWluZyBtb3JlIGR1cmluZyBy dW50aW1lLCB0aGVuIEkgdGhpbmsgdGhlcmUgbXVzdCBiZSBhIG1vcmUKc2VyaW91cyBidWcgc29t ZXdoZXJlLgoKPiAKPiBnb29nbGluZyByZXZlYWxlZCB0aGlzIHBhdGNoOgo+IAo+IAlodHRwOi8v cGVybWFsaW5rLmdtYW5lLm9yZy9nbWFuZS5jb21wLmZyZWVkZXNrdG9wLnhvcmcuZHJpdmVycy5p bnRlbC82NzQ3MQo+IAo+IGlzIHRoZXJlIGFueSByZWFzb24gd2h5IGl0J3Mgbm90IHByZXNlbnQg dXBzdHJlYW0/CgpUaGVyZSdzIGEgdjIgb2YgdGhhdCBwYXRjaCBpbiBzb21lIHRyZWUuIEhtbS4g U2VlbXMgdG8gYmUgaW4KZHJtLWludGVsLW5leHQtcXVldWVkLiBNYXliZSBpdCBzaG91bGQgZ2V0 IGJ1bXBlZCB0byAtZml4ZXM/CgpUaGVyZSdzIGFsc28gYW5vdGhlciBvbmUgdGhhdCBraWxscyBz b21lIG9mIHRob3NlIG1lc3NhZ2Ugb24gY2VydGFpbgpwbGF0Zm9ybXM6CjBmNjQ2MTRkZGUxNyBk cm0vaTkxNTogRml4IGNsb2NrIHJlYWRvdXQgd2hlbiBwaXBlcyBhcmUgZW5hYmxlZCB3L28gcG9y dHMKCi0tIApWaWxsZSBTeXJqw6Rsw6QKSW50ZWwgT1RDCl9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fCkludGVsLWdmeCBtYWlsaW5nIGxpc3QKSW50ZWwtZ2Z4 QGxpc3RzLmZyZWVkZXNrdG9wLm9yZwpodHRwOi8vbGlzdHMuZnJlZWRlc2t0b3Aub3JnL21haWxt YW4vbGlzdGluZm8vaW50ZWwtZ2Z4Cg== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755282AbbJALNQ (ORCPT ); Thu, 1 Oct 2015 07:13:16 -0400 Received: from mga14.intel.com ([192.55.52.115]:2315 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751972AbbJALNN (ORCPT ); Thu, 1 Oct 2015 07:13:13 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,617,1437462000"; d="scan'208";a="817016467" Date: Thu, 1 Oct 2015 14:13:09 +0300 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: Jiri Kosina Cc: maarten.lankhorst@linux.intel.com, linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org, Jani Nikula Subject: Re: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0! Message-ID: <20151001111309.GA26517@intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 01, 2015 at 11:41:34AM +0200, Jiri Kosina wrote: > Hi, > > since I've updated on my thinkpad x200s to latest Linus' tree (3235031), I > am getting a lot of > > [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0! What's a lot? I think you should see at most a few during driver load, and maybe resume. If you're seeing more during runtime, then I think there must be a more serious bug somewhere. > > googling revealed this patch: > > http://permalink.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/67471 > > is there any reason why it's not present upstream? There's a v2 of that patch in some tree. Hmm. Seems to be in drm-intel-next-queued. Maybe it should get bumped to -fixes? There's also another one that kills some of those message on certain platforms: 0f64614dde17 drm/i915: Fix clock readout when pipes are enabled w/o ports -- Ville Syrjälä Intel OTC