From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105308] X log ballooning in size with "drmmode_wait_vblank failed for scanout update" and "get vblank counter failed"
Date: Thu, 01 Mar 2018 11:25:33 +0000 [thread overview]
Message-ID: <bug-105308-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2627 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105308
Bug ID: 105308
Summary: X log ballooning in size with "drmmode_wait_vblank
failed for scanout update" and "get vblank counter
failed"
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: rah@settrans.net
Created attachment 137717
--> https://bugs.freedesktop.org/attachment.cgi?id=137717&action=edit
First 3900 lines of Xorg log
Hi,
My X log is on occassion filling up my hard disk, reaching a size of 18G with
mostly repeats of two lines. The X server is working and running fine; I'm
typing this on it now. The first indication that there is a problem is seeing
"No space left on device". It looks like the woes begin with this line:
[ 668.860] (WW) AMDGPU(0): flip queue failed in amdgpu_scanout_flip: Invalid
argument, TearFree inactive until next modeset
The kernel also reported this although I've no idea when in relation to other
events:
[57903.995504] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR*
amdgpu_cs_list_validate(validated) failed.
[57903.995539] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the
buffer list -22!
[58014.990950] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR*
amdgpu_cs_list_validate(validated) failed.
[58014.990998] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the
buffer list -22!
rah@lotus:~/store-f$ ls -lh Xorg.0.log
-rw-r--r-- 1 rah rah 18G Mar 1 09:52 Xorg.0.log
rah@lotus:~/store-f$ grep "drmmode_wait_vblank failed for scanout update"
Xorg.0.log | head -n 1
[ 668.860] (WW) AMDGPU(0): drmmode_wait_vblank failed for scanout update:
Invalid argument
rah@lotus:~/store-f$ grep "get vblank counter failed" Xorg.0.log | head -n 1
[ 10749.146] (WW) AMDGPU(0): get vblank counter failed: Invalid argument
rah@lotus:~/store-f$ wc -l Xorg.0.log
203212490 Xorg.0.log
rah@lotus:~/store-f$ egrep -vc "(drmmode_wait_vblank failed for scanout
update|get vblank counter failed)" Xorg.0.log
1509
rah@lotus:~/store-f$ grep -c "drmmode_wait_vblank failed for scanout update"
Xorg.0.log
200689290
rah@lotus:~/store-f$ grep -c "get vblank counter failed" Xorg.0.log
2521692
I'll attach the first 3900 lines of the Xorg log and the kernel log.
Thanks,
Bob
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4218 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:[~2018-03-01 11:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 11:25 bugzilla-daemon [this message]
2018-03-01 11:26 ` [Bug 105308] X log ballooning in size with "drmmode_wait_vblank failed for scanout update" and "get vblank counter failed" bugzilla-daemon
2018-03-01 12:03 ` bugzilla-daemon
2018-03-01 12:32 ` bugzilla-daemon
2018-03-01 15:57 ` bugzilla-daemon
2018-03-01 16:10 ` bugzilla-daemon
2018-03-01 16:18 ` bugzilla-daemon
2018-03-01 16:25 ` bugzilla-daemon
2018-03-04 12:30 ` bugzilla-daemon
2018-03-04 12:31 ` bugzilla-daemon
2018-03-04 12:32 ` bugzilla-daemon
2018-03-04 12:36 ` bugzilla-daemon
2018-03-04 12:40 ` bugzilla-daemon
2018-03-08 18:24 ` bugzilla-daemon
2018-03-09 17:29 ` bugzilla-daemon
2018-07-29 18:49 ` bugzilla-daemon
2018-07-30 8:25 ` 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-105308-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.