From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102184] Logs flooded with [drm:drm_mode_addfb2 [drm]] messages
Date: Sat, 12 Aug 2017 12:07:20 +0000 [thread overview]
Message-ID: <bug-102184-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1314 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102184
Bug ID: 102184
Summary: Logs flooded with [drm:drm_mode_addfb2 [drm]] messages
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: libdrm
Assignee: dri-devel@lists.freedesktop.org
Reporter: tech@meikneubauer.de
Ubuntu 16.04HWE kernel 4.10.0-30
libdrm2 version 2.4.76-1~ubuntu16.04.1
lspci excerpt:
00:02.0 VGA compatible controller: Intel Corporation Device 193d (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Amethyst XT [Radeon R9 M295X]
kern.log, syslog and dmesg are flooded with messages like:
[213775.374922] [drm:drm_mode_addfb2 [drm]] [FB:78]
[213775.393105] [drm:drm_mode_addfb2 [drm]] [FB:76]
(always alternating between FB:78 and FB:76)
About 60 such messages per second are issued.
This causes above named log files to grow into Gigabyte range, make them
unusable and cause critical disk shortages on the root filesystem.
Please provide a fix or method to stop these messages.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2616 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-08-12 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 12:07 bugzilla-daemon [this message]
2017-08-14 3:28 ` [Bug 102184] Logs flooded with [drm:drm_mode_addfb2 [drm]] messages bugzilla-daemon
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=bug-102184-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.