From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111211] Kernel 5.2.2 introduced tearing, corruption and freezes with Raven Ridge 2500U
Date: Thu, 15 Aug 2019 17:47:24 +0000 [thread overview]
Message-ID: <bug-111211-502-2RPU1i1Eot@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111211-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 606 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111211
Bráulio Barros de Oliveira <brauliobo@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #7 from Bráulio Barros de Oliveira <brauliobo@gmail.com> ---
the problem is still there and more severe with kernel 5.2.8.
freezes are back also.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2182 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-15 17:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 17:29 [Bug 111211] Kernel 5.2.2 introduced tearing, corruption and freezes with Raven Ridge 2500U bugzilla-daemon
2019-07-24 18:20 ` bugzilla-daemon
2019-07-26 13:54 ` bugzilla-daemon
2019-07-26 13:55 ` bugzilla-daemon
2019-07-26 13:56 ` bugzilla-daemon
2019-07-26 17:00 ` bugzilla-daemon
2019-07-26 17:00 ` bugzilla-daemon
2019-07-29 9:30 ` bugzilla-daemon
2019-07-31 10:02 ` bugzilla-daemon
2019-08-15 17:47 ` bugzilla-daemon [this message]
2019-08-15 17:47 ` [Bug 111211] Kernel 5.2.2+ " bugzilla-daemon
2019-08-30 11:22 ` 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-111211-502-2RPU1i1Eot@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.