Bug 1565931 - Screen freezes for a short time and then resumes when using f28
Summary: Screen freezes for a short time and then resumes when using f28
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: WaylandRelated
TreeView+ depends on / blocked
 
Reported: 2018-04-11 05:14 UTC by deadrat
Modified: 2019-05-28 23:30 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:30:03 UTC


Attachments (Terms of Use)

Description deadrat 2018-04-11 05:14:22 UTC
Description of problem:
The screen freezes for about 3 to 5 seconds and then it starts working again. 
It is easily observable when moving the mouse around (or typing something.) 

The cursor stops responding for few seconds and then it starts moving.  

It happens only in GNOME on Wayland, but works fine in Xorg

Version-Release number of selected component (if applicable):
I am using Version 3.28.0 on fedora 28 and it is uptodate. 

( My hardware is Lenovo Z51 laptop.) 


How reproducible:
Always reproducible

Steps to Reproduce:
1. Freshly install Fedora 28 beta
2. Login to Gnome ( on wayland, which is default)
3. Try launching Firefox and navigate through web, or type something in Gedit or similar actions. 

Actual results:
The screen freezes for about 3 to 5 seconds and then it starts working again. 

It you were moving mouse, the cursor gets stuck. 
If you were typing, the key that got stuck would have typed for about 50 times. 

Expected results:
It responds smoothly. 

Additional info:

Comment 1 Grzegorz 2018-05-14 11:36:47 UTC
I have exactly the same issue.

Comment 2 0xbad 2018-05-16 10:17:33 UTC
Same to me, after upgrading to Fedora 28.

GNOME on Xorg works fine as a temporary workaround!

My Hardware is a Dell Latitude E6540 with a Radeon HD 8790M using the 'radeon' driver and disabled SATA LPM.

After the UI get stuck I _always_ get the following repeating pattern in the kernel log:

Mai 16 11:06:31 heisenberg-localdomain kernel: [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
Mai 16 11:06:31 heisenberg-localdomain kernel: [drm] PCIE gen 3 link speeds already enabled
Mai 16 11:06:31 heisenberg-localdomain kernel: [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
Mai 16 11:06:31 heisenberg-localdomain kernel: radeon 0000:01:00.0: WB enabled
Mai 16 11:06:31 heisenberg-localdomain kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x0000000002c215d3
Mai 16 11:06:31 heisenberg-localdomain kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x00000000c6ceda53
Mai 16 11:06:31 heisenberg-localdomain kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x00000000ce94ab41
Mai 16 11:06:31 heisenberg-localdomain kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x00000000b948be14
Mai 16 11:06:31 heisenberg-localdomain kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x00000000fffb6182
Mai 16 11:06:31 heisenberg-localdomain kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x0000000006475b5e
Mai 16 11:06:31 heisenberg-localdomain kernel: radeon 0000:01:00.0: failed VCE resume (-110).
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ring test on 0 succeeded in 1 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ring test on 1 succeeded in 1 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ring test on 2 succeeded in 1 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ring test on 3 succeeded in 4 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ring test on 4 succeeded in 3 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ring test on 5 succeeded in 2 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] UVD initialized successfully.
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ib test on ring 2 succeeded in 0 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Mai 16 11:06:32 heisenberg-localdomain kernel: [drm] ib test on ring 5 succeeded


A re-installation of _all_ packages did not solve the issue.

Comment 3 Richard Janík 2018-05-24 10:26:35 UTC
I see there are multiple issues which seem related to this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1563811
https://bugzilla.redhat.com/show_bug.cgi?id=1566240
https://bugzilla.redhat.com/show_bug.cgi?id=1575281

I'm also running into these issues after I updated Fedora 27 to Fedora 28 this morning (using GNOME 3, Wayland as it is the default). My symptoms:

1, Occasional short system freeze (~1s) after input - after I move the mouse pointer, or after I start typing. Doesn't seem related to notifications as said in the first mentioned report. `gnome-shell` always shoots up to the first place in CPU usage in `top` when this freeze happens. Inputs are multiplied during this freeze (a key press is repeated several times) and sound outputs sometimes freeze as well.

2, After locking the screen, and having it locked for some time (more than a minute?) the system sometimes (2 out of 4 times so far) freezes entirely when I unlock the screen. The screen stays frozen after being unlocked and the mouse pointer doesn't move, keyboard doesn't work. Switching between consoles (Ctrl+Alt+F2) doesn't work either, I had to hard restart the system by holding the power button down. No one else reported this, unless I missed it. If you want another bug filed for this, let me know.

I wasn't able to get any backtraces as the system either resumes after a while or the system dies entirely. If you want some logs, let me know. If you need any other help reproducing these issues, please let me know what I need to do and I'll help.

Comment 4 Christian Stadelmann 2018-05-31 10:40:37 UTC
I see this issue too. It happens more often when showing notifications (see bug #1563811) and when opening any URL from my RSS reader (see bug #1575281).

(In reply to Richard Janík from comment #3)
> […]

Thanks for the links! I can reproduce your symptom #1 too.

Comment 5 Kamil Pawlowski 2018-06-07 10:34:56 UTC
I'm using HP ProBook 6740b.

I have the same issue on both Wayland and X.Org.
Freezes when a notification appears, also on occasion in different situations.

Sometimes even whole server was crashing. Really looks like it is some problems with a graphics driver or graphics related component

I have never experiencing such problems before f28 (on my laptop since f24)

Comment 6 Jonas Ådahl 2018-06-07 10:45:26 UTC
Does any of these issues go away with https://copr.fedorainfracloud.org/coprs/jadahl/mutter-hw-cursor-on-demand/build/758884/ ?

Comment 7 Christian Stadelmann 2018-06-09 10:07:04 UTC
(In reply to Jonas Ådahl from comment #6)
> Does any of these issues go away with
> https://copr.fedorainfracloud.org/coprs/jadahl/mutter-hw-cursor-on-demand/
> build/758884/ ?

The freeze after clicking an URL (bug #1575281) does not go away, I still see freezes for several seconds. It may happen less often (I'm not sure about that though).

The freeze when showing a notification is still present but got less worse, i.e. it freezes only for 100…500ms (only noticable if you move your mouse while the notification is shown) instead of several seconds.

I'm using Fedora 28 with GNOME/wayland.

Comment 8 Ben Cotton 2019-05-02 20:05:39 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2019-05-28 23:30:03 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.