答复: System freeze on display re-activation persists

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 at lists.freedesktop.org> 代表 Martin Babutzka <martin.babutzka at 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 at 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 at lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/amd-gfx


[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux