From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194645] amdgpu: amdgpu_resume failed
Date: Tue, 21 Feb 2017 16:21:06 +0000 [thread overview]
Message-ID: <bug-194645-2300-pBxNwtFmWx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194645-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194645
Christian König (deathsimple@vodafone.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |deathsimple@vodafone.de
--- Comment #5 from Christian König (deathsimple@vodafone.de) ---
(In reply to Mateusz Lenik from comment #4)
> I did try to bisect, but wasn't very successful. It reported totally
> unrelated commit as the first “bad” commit.
>
> I'm sure that resume for amdgpu works correctly on v4.9 and is broken on
> 4.10-rc1
Make sure that reboot to the correct kernel after each retry.
On Ubuntu I usually change /etc/grub.d/10_linux to automatically boot into the
latest installed kernel and not the one with the highest version number as
well.
--
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:[~2017-02-21 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 8:31 [Bug 194645] New: amdgpu: amdgpu_resume failed bugzilla-daemon
2017-02-21 8:32 ` [Bug 194645] " bugzilla-daemon
2017-02-21 8:41 ` bugzilla-daemon
2017-02-21 9:05 ` bugzilla-daemon
2017-02-21 16:15 ` bugzilla-daemon
2017-02-21 16:21 ` bugzilla-daemon [this message]
2017-02-21 16:32 ` bugzilla-daemon
2017-02-21 16:41 ` bugzilla-daemon
2017-02-21 16:53 ` bugzilla-daemon
2017-02-21 18:09 ` bugzilla-daemon
2017-02-22 2:10 ` 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-194645-2300-pBxNwtFmWx@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