From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96866] REGRESSION System frozen after resume
Date: Sat, 09 Jul 2016 23:34:38 +0000 [thread overview]
Message-ID: <bug-96866-502-k6MULF5NLg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96866-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 846 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96866
Christopher M. Penalver <christopher.m.penalver@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|System frozen after resume, |REGRESSION System frozen
|on Ubuntu 16.04 kernel |after resume
|4.4.0-22 |
Severity|critical |normal
--- Comment #1 from Christopher M. Penalver <christopher.m.penalver@gmail.com> ---
1) Edited title as not a Ubuntu bug, but an upstream one as per original
reporter (reproducible in mainline 4.7-rc6 and a regression).
2) Issue after suspend isn't Critical.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2235 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 prev parent reply other threads:[~2016-07-09 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 22:38 [Bug 96866] System frozen after resume, on Ubuntu 16.04 kernel 4.4.0-22 bugzilla-daemon
2016-07-09 23:34 ` bugzilla-daemon [this message]
2016-08-01 18:13 ` [Bug 96866] REGRESSION System frozen after resume bugzilla-daemon
2016-08-01 18:16 ` bugzilla-daemon
2016-09-06 8:43 ` bugzilla-daemon
2016-11-27 15:01 ` bugzilla-daemon
2017-12-20 17:59 ` 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-96866-502-k6MULF5NLg@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