From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80141] Fails to page flip multiple time, queue overflows waiting for one to finish that never does crashing entire system.
Date: Sun, 29 Jun 2014 04:36:03 +0000 [thread overview]
Message-ID: <bug-80141-502-fcWUHuABW3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-80141-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2136 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=80141
--- Comment #15 from Aaron B <aaronbottegal@gmail.com> ---
> Bug #2: This was triggered by Chromium, when resizing the window/dragging
> with the mouse on the top of the screen. This one particular time made the
> screen jump, like I've also seen in Steam, but this one triggers a black
> scanline, (very very rarely) accompanied by a slight (1px vertical) tear
> upwards at the scanline the black line is on. They happen more towards the
> bottom and middle of the screen, although they start at the top. It happened
> once every 10 seconds or so when it started, but now is happening 1-2 times
> a second sometimes with multiple black lines in the same frame it seems. The
> black line occurence is increasing as time goes on. This was VERY common in
> 3.14 kernel, so the issue probably is just being put off by the new dri
> implementation I was given to test, but still exists. I don't really know
> weather to make a new bug report or not specifically for that, I don't
> really know what components to look at either. Any ideas, tests, etc. I can
> do them. But still, this has seemed to fix the random complete failure
> crashes. Or, maybe with the black lines, has just delayed them. I can't
> really tell.
This seems to be caused by Chromium, BUT. I believe the colors being sent to
the screen were affecting it. Looking at my desktop, the lines were not on the
screen. They used to be in 3.14, though, even on the desktop. But, with this
glitch they were not. I opened Libreoffice, with mainly white pixels on the
left side, flipped the screen 180 degrees, and...turning off the on HDMI, or
whatever it does to the display when it flipped, fixed it, and now it's back to
normal. But, like I said, I would wager the glitch was caused by pixel colors,
or maybe colors were looked at as commands and the pixel clock frequency is a
tad off. I'm not 100% sure on any of it, just saying what fixed it for me so if
it's looked in to, it can help. If I could make a new bug report just for that,
I will.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3297 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-06-29 4:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 15:22 [Bug 80141] New: Fails to page flip multiple, queue overflows waiting for one to finish that never does crashing entire system bugzilla-daemon
2014-06-17 15:25 ` [Bug 80141] " bugzilla-daemon
2014-06-17 16:09 ` [Bug 80141] Fails to page flip multiple time, " bugzilla-daemon
2014-06-17 16:34 ` bugzilla-daemon
2014-06-17 17:53 ` bugzilla-daemon
2014-06-19 18:42 ` bugzilla-daemon
2014-06-22 22:28 ` bugzilla-daemon
2014-06-23 18:50 ` bugzilla-daemon
2014-06-24 2:51 ` bugzilla-daemon
2014-06-24 6:25 ` bugzilla-daemon
2014-06-24 18:22 ` bugzilla-daemon
2014-06-25 3:38 ` bugzilla-daemon
2014-06-27 2:51 ` bugzilla-daemon
2014-06-27 3:06 ` bugzilla-daemon
2014-06-27 6:49 ` bugzilla-daemon
2014-06-29 4:27 ` bugzilla-daemon
2014-06-29 4:36 ` bugzilla-daemon [this message]
2014-07-02 5:37 ` bugzilla-daemon
2014-07-09 15:42 ` bugzilla-daemon
2014-07-10 7:27 ` bugzilla-daemon
2014-07-10 7:29 ` 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-80141-502-fcWUHuABW3@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 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).