* System freeze on display re-activation persists
@ 2017-11-02 6:36 Martin Babutzka
[not found] ` <1509604577.1928.9.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
0 siblings, 1 reply; 4+ messages in thread
From: Martin Babutzka @ 2017-11-02 6:36 UTC (permalink / raw)
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW
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
^ permalink raw reply [flat|nested] 4+ messages in thread[parent not found: <1509604577.1928.9.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>]
* Re: System freeze on display re-activation persists [not found] ` <1509604577.1928.9.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org> @ 2017-11-02 13:38 ` Alex Deucher [not found] ` <CADnq5_NCKycvFz_okprcV_FRaJG7szF=FKCosM=k9DL_U1pOYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Alex Deucher @ 2017-11-02 13:38 UTC (permalink / raw) To: Martin Babutzka; +Cc: amd-gfx list On Thu, Nov 2, 2017 at 2:36 AM, Martin Babutzka <martin.babutzka@online.de> wrote: > 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? It was reported and confirmed that this patch fixes it: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-next&id=ddabbf65aae36e21b4c79354940f80eae6c36104 I'm running a tonga board now and have no problems with dpms. Alex > > Many regards, > Martin > _______________________________________________ > amd-gfx mailing list > amd-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CADnq5_NCKycvFz_okprcV_FRaJG7szF=FKCosM=k9DL_U1pOYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: System freeze on display re-activation persists [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> 0 siblings, 1 reply; 4+ messages in thread From: Martin Babutzka @ 2017-11-05 18:20 UTC (permalink / raw) To: Alex Deucher, amd-gfx list [-- Attachment #1: Type: text/plain, Size: 2122 bytes --] Dear developers, Unfortunately I cannot confirm that the issue is fully resolved. I built the amd-staging-drm-next including the mentioned commit. Crashes are still likely to happen when I try to resume from suspend. The system freeze can show a black screen or a weird pattern like attached. There is hardly any log message that helps all relevant logs end up with a large number of "^@" symbols. Any further recommendations of branches to test or settings to change? Do I have to enable dpms manually? Many regards, Martin Am Donnerstag, den 02.11.2017, 09:38 -0400 schrieb Alex Deucher: > On Thu, Nov 2, 2017 at 2:36 AM, Martin Babutzka > <martin.babutzka-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org> wrote: > > 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? > > It was reported and confirmed that this patch fixes it: > https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-n > ext&id=ddabbf65aae36e21b4c79354940f80eae6c36104 > > I'm running a tonga board now and have no problems with dpms. > > Alex > > > > > Many regards, > > Martin > > _______________________________________________ > > amd-gfx mailing list > > amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org > > https://lists.freedesktop.org/mailman/listinfo/amd-gfx [-- Attachment #2: shrinked-IMG_20171103_184418.jpg --] [-- Type: image/jpeg, Size: 450202 bytes --] [-- Attachment #3: crash_xorg_log.txt --] [-- Type: text/plain, Size: 13325 bytes --] [ 103.092] (II) AIGLX: Suspending AIGLX clients for VT switch [ 109.920] (II) AIGLX: Resuming AIGLX clients after VT switch [ 109.925] (II) modeset(0): EDID vendor "ACR", prod id 134 [ 109.925] (II) modeset(0): Using hsync ranges from config file [ 109.925] (II) modeset(0): Using vrefresh ranges from config file [ 109.925] (II) modeset(0): Printing DDC gathered Modelines: [ 109.925] (II) modeset(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1110 -hsync -vsync (66.6 kHz eP) [ 109.925] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) [ 109.925] (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) [ 109.925] (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 109.925] (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 109.925] (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 109.925] (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [ 109.925] (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [ 109.925] (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) [ 109.925] (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) [ 109.925] (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 109.925] (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) [ 109.925] (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [ 109.925] (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [ 109.925] (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) [ 109.925] (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 109.925] (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) [ 109.925] (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [ 109.925] (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) [ 109.925] (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [ 109.925] (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 109.925] (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) [ 109.925] (II) modeset(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) [ 109.925] (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) [ 109.925] (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) [ 109.925] (II) modeset(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) [ 109.925] (II) modeset(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz e) [ 109.925] (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) [ 109.925] (II) modeset(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) [ 109.925] (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) [ 109.926] (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) [ 109.926] (II) modeset(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) [ 109.927] (II) event2 - (II) Power Button: (II) is tagged by udev as: Keyboard [ 109.927] (II) event2 - (II) Power Button: (II) device is a keyboard [ 109.927] (II) event1 - (II) Power Button: (II) is tagged by udev as: Keyboard [ 109.927] (II) event1 - (II) Power Button: (II) device is a keyboard [ 109.927] (II) event0 - (II) Sleep Button: (II) is tagged by udev as: Keyboard [ 109.927] (II) event0 - (II) Sleep Button: (II) device is a keyboard [ 109.928] (II) event3 - (II) Microsoft Microsoft® SiderWinderTM X4 Keyboard: (II) is tagged by udev as: Keyboard [ 109.928] (II) event3 - (II) Microsoft Microsoft® SiderWinderTM X4 Keyboard: (II) device is a keyboard [ 109.928] (II) event4 - (II) Microsoft Microsoft® SiderWinderTM X4 Keyboard: (II) is tagged by udev as: Keyboard [ 109.928] (II) event4 - (II) Microsoft Microsoft® SiderWinderTM X4 Keyboard: (II) device is a keyboard [ 109.992] (II) event5 - (II) Logitech Gaming Mouse G400: (II) is tagged by udev as: Mouse [ 109.992] (II) event5 - (II) Logitech Gaming Mouse G400: (II) device set to 800 DPI [ 109.992] (II) event5 - (II) Logitech Gaming Mouse G400: (II) device is a pointer ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ [-- Attachment #4: Type: text/plain, Size: 154 bytes --] _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <1509906015.1928.6.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>]
* 答复: System freeze on display re-activation persists [not found] ` <1509906015.1928.6.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org> @ 2017-11-06 2:35 ` Qu, Jim 0 siblings, 0 replies; 4+ messages in thread From: Qu, Jim @ 2017-11-06 2:35 UTC (permalink / raw) To: Martin Babutzka, Alex Deucher, amd-gfx list Hi Martin: The log do not have any useful information. For S3 issue I think you can do: 1. Do you have any other AMD GFX? such as Bonaire or Tonga. Please have a try with the some driver. 2. Do you have a chance to set up com port? The com port is very useful for debugging S3 issue. a. add "console=ttyS0,115200,8N1 console=tty1 no_console_suspend" to GRUB_CMDLINE_LINUX in kernel grub. then update-grub b. echo 7 > /proc/sys/kernel/printk, then perform S3. Thanks JimQu ________________________________________ 发件人: amd-gfx <amd-gfx-bounces@lists.freedesktop.org> 代表 Martin Babutzka <martin.babutzka@online.de> 发送时间: 2017年11月6日 2:20 收件人: Alex Deucher; amd-gfx list 主题: Re: System freeze on display re-activation persists Dear developers, Unfortunately I cannot confirm that the issue is fully resolved. I built the amd-staging-drm-next including the mentioned commit. Crashes are still likely to happen when I try to resume from suspend. The system freeze can show a black screen or a weird pattern like attached. There is hardly any log message that helps all relevant logs end up with a large number of "^@" symbols. Any further recommendations of branches to test or settings to change? Do I have to enable dpms manually? Many regards, Martin Am Donnerstag, den 02.11.2017, 09:38 -0400 schrieb Alex Deucher: > On Thu, Nov 2, 2017 at 2:36 AM, Martin Babutzka > <martin.babutzka@online.de> wrote: > > 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? > > It was reported and confirmed that this patch fixes it: > https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-n > ext&id=ddabbf65aae36e21b4c79354940f80eae6c36104 > > I'm running a tonga board now and have no problems with dpms. > > Alex > > > > > Many regards, > > Martin > > _______________________________________________ > > amd-gfx mailing list > > amd-gfx@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/amd-gfx _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx ^ permalink raw reply [flat|nested] 4+ messages in thread
![[-- Attachment #2: shrinked-IMG_20171103_184418.jpg --] [-- Type: image/jpeg, Size: 450202 bytes --]](../../1509906015.1928.6.camel@online.de/2-shrinked-IMG_20171103_184418.jpg){kind=link}
end of thread, other threads:[~2017-11-06 2:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-02 6:36 System freeze on display re-activation persists Martin Babutzka
[not found] ` <1509604577.1928.9.camel-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org>
2017-11-02 13:38 ` 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
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.