From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Dave Jones <davej@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Linux Kernel <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, Dave Airlie <airlied@redhat.com>,
Paulo Zanoni <paulo.r.zanoni@intel.com>,
Rob Clark <rob.clark@linaro.org>
Subject: Re: Lots of i915/drm spew on 3.4
Date: Sun, 3 Jun 2012 17:17:15 +0200 [thread overview]
Message-ID: <20120603151715.GB4696@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGTP5S9Az5oHMxYgyJbDPv9R7gRoC614RW0OLk7_TBeDZQ@mail.gmail.com>
On Thu, May 31, 2012 at 10:22:28AM -0300, Paulo Zanoni wrote:
> 2012/5/31 Chris Wilson <chris@chris-wilson.co.uk>:
> > Before that commit we had no idea that we had run out of property slots.
> > I think the WARN is genuine, but maybe we should just bump the count set
> > it to WARN_ONCE and hope the conversion to lists arrives sooner rather
> > than latter.
> > -Chris
> >
>
> Chris is right: this is not a regression. Before that patch, no one
> checked if property creation really worked. I chose not to use
> WARN_ONCE because we need to increase the variable once for each time
> you see the message. Assuming this message appears on your log less
> than 8 times, does this patch fix your problem?
>
> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
> index 73e4560..bac55c2 100644
> --- a/include/drm/drm_crtc.h
> +++ b/include/drm/drm_crtc.h
> @@ -54,7 +54,7 @@ struct drm_mode_object {
> struct drm_object_properties *properties;
> };
>
> -#define DRM_OBJECT_MAX_PROPERTY 16
> +#define DRM_OBJECT_MAX_PROPERTY 24
> struct drm_object_properties {
> int count;
> uint32_t ids[DRM_OBJECT_MAX_PROPERTY];
I've hit the same warn on my g33 with a tv-out sdvo. Seems to be enough to
shut it up.
Tested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-06-03 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 21:31 Dave Jones
2012-05-30 21:51 ` Daniel Vetter
2012-05-30 21:58 ` Dave Jones
2012-05-30 22:26 ` Dave Jones
2012-05-31 7:59 ` Chris Wilson
2012-05-31 13:22 ` Paulo Zanoni
2012-06-03 15:17 ` Daniel Vetter [this message]
2012-05-31 14:43 ` Paulo Zanoni
2012-06-03 13:27 ` Daniel Vetter
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=20120603151715.GB4696@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=davej@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.com \
--cc=rob.clark@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®