From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] 4.17-rc2: Could not determine valid watermarks for inherited state
Date: Thu, 26 Apr 2018 17:56:14 +0300 [thread overview]
Message-ID: <20180426145614.GP23723@intel.com> (raw)
In-Reply-To: <20180426142719.fzivt2e6kialcbp4@codemonkey.org.uk>
On Thu, Apr 26, 2018 at 10:27:19AM -0400, Dave Jones wrote:
> [ 1.176131] [drm:i9xx_get_initial_plane_config] pipe A/primary A with fb: size=800x600@32, offset=0, pitch 3200, size 0x1d4c00
> [ 1.176161] [drm:i915_gem_object_create_stolen_for_preallocated] creating preallocated stolen object: stolen_offset=0x0000000000000000, gtt_offset=0x0000000000000000, size=0x00000000001d5000
> [ 1.176312] [drm:intel_alloc_initial_plane_obj.isra.127] initial plane fb obj (ptrval)
> [ 1.176351] [drm:intel_modeset_init] pipe A active planes 0x1
> [ 1.176456] [drm:drm_atomic_helper_check_plane_state] Plane must cover entire CRTC
> [ 1.176481] [drm:drm_rect_debug_print] dst: 800x600+0+0
> [ 1.176494] [drm:drm_rect_debug_print] clip: 1366x768+0+0
OK, so that's the problem right there. The fb we took over from the
BIOS was 800x600, but now we're trying to set up a 1366x768 mode.
We seem to be missing checks to make sure the initial fb is actually
big enough for the mode we're currently using :(
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2018-04-26 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 15:27 4.17-rc2: Could not determine valid watermarks for inherited state Dave Jones
2018-04-26 12:47 ` Jani Nikula
2018-04-26 13:10 ` [Intel-gfx] " Ville Syrjälä
2018-04-26 14:27 ` Dave Jones
2018-04-26 14:56 ` Ville Syrjälä [this message]
2018-04-26 15:16 ` Ville Syrjälä
2018-04-26 15:25 ` Ville Syrjälä
2018-04-26 15:57 ` Dave Jones
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=20180426145614.GP23723@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=davej@codemonkey.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).