From: Martin Babutzka <martin.babutzka-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: System freeze on display re-activation persists
Date: Thu, 02 Nov 2017 07:36:17 +0100 [thread overview]
Message-ID: <1509604577.1928.9.camel@online.de> (raw)
Dear AMD developers,
I wanted to mention that the regression in amd-staging-drm-next which I
reported on the 29.09. and the 06.10. still exists with the latest tree
state of the branch.
A crash/freeze occurs after the screen is re-enabled either from
suspend or from screen locking (which shuts off the display as well).
The system lock-timing varies: It can get stuck at a blank screen, at
the login screen or even shortly after a login.
The kernel is the unmodified amd-staging-drm-next running with my Tonga
GPU. It does not occur in the official 4.13 kernel of Ubuntu 17.10.
Unfortunately I failed to bisect it to the causing commit but the issue
is there for a pretty long time in the 4.13 kernel, most likely merged
into the code before 10.09.
Did nobody else from this mailing list experience the same issue?
Many regards,
Martin
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2017-11-02 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 6:36 Martin Babutzka [this message]
[not found] ` <1509604577.1928.9.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
2017-11-02 13:38 ` System freeze on display re-activation persists Alex Deucher
[not found] ` <CADnq5_NCKycvFz_okprcV_FRaJG7szF=FKCosM=k9DL_U1pOYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-05 18:20 ` Martin Babutzka
[not found] ` <1509906015.1928.6.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
2017-11-06 2:35 ` 答复: " Qu, Jim
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=1509604577.1928.9.camel@online.de \
--to=martin.babutzka-bgeptl67xyczqb+pc5nmwq@public.gmane.org \
--cc=amd-gfx-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.