dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 05 May 2018 09:09:18 +0000	[thread overview]
Message-ID: <bug-199025-2300-gEwlQQp6gh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199025-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=199025

Patrice Poly (p.polypa@free.fr) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |p.polypa@free.fr

--- Comment #19 from Patrice Poly (p.polypa@free.fr) ---
Hello,

I am having the exact same issue on an intel Q6600 , under fedora 28 , 

kernel : 4.16.5-300.fc28.x86_64

In a fresh Fedora 28 install, ( which has runlevel 5 as default ) suspend
blanks the screen and disables any input, forcing to a hard restart using the
power button. 
Reproductible : always

I am using nouveau : 

Name         : xorg-x11-drv-nouveau
Epoch        : 1
Version      : 1.0.15
Release      : 4.fc28
Arch         : x86_64
Size         : 229 k
Source       : xorg-x11-drv-nouveau-1.0.15-4.fc28.src.rpm
Repo         : @System
From repo    : anaconda
Summary      : Xorg X11 nouveau video driver for NVIDIA graphics chipsets
URL          : http://www.x.org
License      : MIT
Description  : X.Org X11 nouveau video driver.

Setting runlevel defaults to 3 and launching x with startx fixes the issue,
which is perfectly acceptable for me as a workaround. Thank you very much @todd
for the hint.

I'd be glad to provide additional info if it can help.

-- 
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

  parent reply	other threads:[~2018-05-05  9:09 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 [this message]
2018-05-05  9:56 ` bugzilla-daemon
2018-05-06 17:24 ` bugzilla-daemon
2018-05-08  5:17 ` bugzilla-daemon
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-gEwlQQp6gh@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