From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
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 [thread overview]
Message-ID: <20151001111309.GA26517@intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1510011124030.30132@pobox.suse.cz>
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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: maarten.lankhorst@linux.intel.com, linux-kernel@vger.kernel.org,
intel-gfx@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>
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 [thread overview]
Message-ID: <20151001111309.GA26517@intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1510011124030.30132@pobox.suse.cz>
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
next prev parent reply other threads:[~2015-10-01 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 9:41 [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0! Jiri Kosina
2015-10-01 11:13 ` Ville Syrjälä [this message]
2015-10-01 11:13 ` Ville Syrjälä
2015-10-01 14:42 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151001111309.GA26517@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.