From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.
Date: Tue, 08 May 2018 05:17:58 +0000 [thread overview]
Message-ID: <bug-199025-2300-uCWj5vtzqd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199025-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199025
todd (toddsmb@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Kernel Version|4.15.x |4.15.x and 4.16.x
--- Comment #22 from todd (toddsmb@gmail.com) ---
@Chen,
I'm going to be tied up for a few weeks, due to a larger than normal workload.
So I won't have time to mess with this bug right now.
In the mean time I will try blacklisting all vid drivers and see what happens.
Although I suspect it will act the same as when the X display manager is
disabled by setting multi-user.target.
But I know it won't be any time this week. Maybe mid next week if I'm lucky.
For the time being though, there are 3 work-arounds listed here that fix the
problem.
1) Change runlevel from 5 to 3 (permanent fix - see opening post + comment #6).
2) Restart your X display manager once you log in. For instance Xfce spins use
Lightdm. (Temporary fix that lasts until the system is rebooted).
* See comemnt #16
3) Install another video driver and blacklist Nouveau (permanent fix but a big
hassle if you run secure boot).
* see comment #5 for manual Nvidia driver install or see comment #7 for
external repository to install Nvidia driver.
I personally don't know anything about the repo listed in comment #7. Whereas
in comment #5, you are downloading directly from Nvidia themselves.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-08 5:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199025-2300@https.bugzilla.kernel.org/>
2018-05-04 8:35 ` [Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state bugzilla-daemon
2018-05-05 9:09 ` bugzilla-daemon
2018-05-05 9:56 ` bugzilla-daemon
2018-05-06 17:24 ` bugzilla-daemon
2018-05-08 5:17 ` bugzilla-daemon [this message]
2018-05-08 5:28 ` bugzilla-daemon
2018-05-08 6:31 ` bugzilla-daemon
2018-05-08 6:51 ` bugzilla-daemon
2018-05-08 7:10 ` bugzilla-daemon
2018-05-08 7:12 ` bugzilla-daemon
2018-05-08 8:36 ` bugzilla-daemon
2018-05-08 9:42 ` bugzilla-daemon
2018-05-08 18:58 ` bugzilla-daemon
2018-05-08 19:51 ` bugzilla-daemon
2018-05-09 0:06 ` bugzilla-daemon
2018-05-09 0:10 ` bugzilla-daemon
2018-05-09 4:28 ` bugzilla-daemon
2018-05-10 4:08 ` bugzilla-daemon
2018-05-10 4:27 ` bugzilla-daemon
2018-06-12 19:39 ` bugzilla-daemon
2018-06-14 12:46 ` bugzilla-daemon
2018-06-14 20:20 ` bugzilla-daemon
2018-10-17 3:23 ` [Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state. - Asus PRIME Z270-P bugzilla-daemon
2018-11-09 2:51 ` [Bug 199025] Suspend hangs with Nouveau loaded. " 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-199025-2300-uCWj5vtzqd@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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).