public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: poma <pomidorabelisima@gmail.com>
To: Mailing-List fedora-kernel <kernel@lists.fedoraproject.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: VGA resume & thaw (wake up from S3 & S4) broken - kernel exclusively
Date: Sat, 13 Sep 2014 06:57:09 +0200	[thread overview]
Message-ID: <5413CEA5.3060403@gmail.com> (raw)


Actually I have nothing to show cause logs are all OK.
Haha, it seems to me that the bugs become intelligent.

3.15.10-201.fc20.x86_64
3.16.2-200.fc20.x86_64
3.17.0-0.rc4.git3.2.fc22.1.x86_64
 nouveau  [     DRM] suspending display...
 nouveau  [     DRM] unpinning framebuffer(s)...
 nouveau  [     DRM] evicting buffers...
 nouveau  [     DRM] waiting for kernel channels to go idle...
 nouveau  [     DRM] suspending client object trees...
 nouveau  [     DRM] suspending kernel object tree...
...
 nouveau  [     DRM] re-enabling device...
 nouveau  [     DRM] resuming kernel object tree...
 nouveau  [   VBIOS][0000:02:00.0] running init tables
 nouveau  [  PTHERM][0000:02:00.0] fan management: automatic
 nouveau  [     CLK][0000:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz
 nouveau  [     DRM] resuming client object trees...
 nouveau  [     DRM] resuming display...
 nouveau 0000:02:00.0: no hotplug settings from platform
 nouveau 0000:02:00.0: no hotplug settings from platform

Logs(dmesg) are literally identical.

3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works.
        Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN
            ALL Kernels - vesa(fb)    resume & thaw BROKEN.


Have a nice weekend folks.


poma


             reply	other threads:[~2014-09-13  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13  4:57 poma [this message]
2014-09-13  5:02 ` VGA resume & thaw (wake up from S3 & S4) broken - kernel exclusively poma

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=5413CEA5.3060403@gmail.com \
    --to=pomidorabelisima@gmail.com \
    --cc=kernel@lists.fedoraproject.org \
    --cc=linux-kernel@vger.kernel.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