All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99889] nouveau preventing shutdown after suspend-resume
Date: Tue, 18 Jul 2017 07:04:29 +0000	[thread overview]
Message-ID: <bug-99889-8800-DIfCJC2Qnd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99889-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 712 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99889

--- Comment #6 from Olivier van der Toorn <oliviervdtoorn+freedesktop@gmail.com> ---
I can confirm this bug happens too on an Asus X556UQK machine running Gentoo.
Currently running the latest kernel (4.13_rc1), and the bug is still present.

What I think has the same cause, is that when the laptop awakes from suspend,
the screen is frozen after some 30 seconds after the waking up. It freezes for
about ten seconds, and then continues as if nothing happened. After that in
dmesg the line:

nouveau 0000:01:00.0: DRM: failed to idle channel 0 [DRM]

shows up in red.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1517 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-07-18  7:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-99889-8800@http.bugs.freedesktop.org/>
     [not found] ` <bug-99889-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-02-21 16:04   ` [Bug 99889] nouveau preventing shutdown after suspend-resume bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-20 10:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-22 22:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-03  8:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-11 15:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-15  4:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-18  7:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-08-01  5:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-29 15:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-17 22:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-10 14:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-30  1:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-02 13:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-30  1:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-21 15:58 bugzilla-daemon
2017-02-21 16:04 ` 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-99889-8800-DIfCJC2Qnd@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.