All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 117181] graphic glitches for Kernel > 4.2 Intel HD 5xx and skylake
Date: Mon, 25 Apr 2016 19:58:17 +0000	[thread overview]
Message-ID: <bug-117181-2300-jyoGunWFx5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-117181-2300@https.bugzilla.kernel.org/>

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

--- Comment #1 from yves.dufournaud@gmail.com ---
there is another issue: resuming from suspend to ram is failing, I would have
filled a separate bug, but apparently it can be linked to graphics.

following the instruction here:
https://01.org/linuxgraphics/documentation/development/how-debug-suspend-resume-issues

S3 suspend (a.k.a Suspend To RAM):
dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after

the machine go to sleep : led blinking
after pressing power button, make machine reboot.
but dmesg_after exists with same content as dmesg_before, so quoting source:

"If dmesg_after exists, it means that the system can be resumed from BIOS, so
it's likely to be a graphics issue. Otherwise, it's not related to graphics and
don't report it to freedesktop.org bugzilla."

will try to set Enable "CONFIG_PM_DEBUG" for next test

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

  reply	other threads:[~2016-04-25 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 16:22 [Bug 117181] New: graphic glitches for Kernel > 4.2 Intel HD 5xx and skylake bugzilla-daemon
2016-04-25 19:58 ` bugzilla-daemon [this message]
2016-04-25 20:58 ` [Bug 117181] " bugzilla-daemon
2016-04-25 20:59 ` bugzilla-daemon
2016-04-28 11:38 ` bugzilla-daemon
2016-10-26 12:41 ` 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-117181-2300-jyoGunWFx5@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 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.