All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Massimo B." <massimo.b@gmx.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [drm] Reducing the compressed framebuffer size
Date: Wed, 13 May 2020 15:29:43 +0300	[thread overview]
Message-ID: <20200513122943.GC6112@intel.com> (raw)
In-Reply-To: <56fb2eaf4241f80799f25733c242489e00c6021a.camel@gmx.net>

On Tue, May 12, 2020 at 03:36:01PM +0200, Massimo B. wrote:
> Hello everybody,
> 
> since Kernel 5.6.5 I encounter many syslog lines like
> 
> [kernel] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
>                 - Last output repeated 4 times -
> 
> I found some explanation at:
> https://wiki.archlinux.org/index.php/intel_graphics#Framebuffer_compression_(enable_fbc)
> But why do I get this with a i7-4790 Haswell, which is not pre-Sandy?

FBC is a thing for all platform generations.

> 
> Anyway I followed the hint and set
> 
> # cat /etc/modprobe.d/i915.conf
> options i915 enable_fbc=0
> 
> After reboot the setting seems active:
> 
> # cat /sys/module/i915/parameters/enable_fbc
> 0
> 
> But I still get the same logs. Which BIOS setting is responsible, how can I fix
> that? Is there a better place to ask?

There is a patch on its way somewhere to linus/stable trees to eliminate
this dmesg spam:
https://cgit.freedesktop.org/drm-intel/commit/?id=6b7fc6a3e6af4ff5773949d0fed70d8e7f68d5ce

But it's a bit strange you still get it with fbc disabled. The logic
for when to allocate the cfb may be a bit busted atm...

> 
> # lspci |grep VGA
> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
> 
> # grep name /proc/cpuinfo |tail -n1
> model name	: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
> 
> Best regards,
> Massimo
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2020-05-13 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 13:36 [drm] Reducing the compressed framebuffer size Massimo B.
2020-05-13 12:29 ` Ville Syrjälä [this message]

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=20200513122943.GC6112@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=massimo.b@gmx.net \
    /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.