Bug 100351

Summary:	System freezes for 2 seconds while opening apps
Product:	Drivers	Reporter:	yaroslav.sapozhnik
Component:	Video(DRI - non Intel)	Assignee:	drivers_video-dri
Status:	NEW ---
Severity:	normal	CC:	alexdeucher, yaroslav.sapozhnik, zz1844928
Priority:	P1
Hardware:	x86-64
OS:	Linux
Kernel Version:	4.0.5-300.fc22.x86_64	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	dmesg Xorg log

Description yaroslav.sapozhnik 2015-06-22 21:48:12 UTC

Every time I open KDE app, the system freezes for 2 seconds. 

It has 2 graphic cards:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff)

In the logs I see:
Jun 22 17:33:25 terminus kernel: [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
Jun 22 17:33:25 terminus kernel: [drm] PCIE gen 3 link speeds already enabled
Jun 22 17:33:25 terminus kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000277000).
Jun 22 17:33:25 terminus kernel: radeon 0000:01:00.0: WB enabled
Jun 22 17:33:25 terminus kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88041697cc00
Jun 22 17:33:25 terminus kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88041697cc04
Jun 22 17:33:25 terminus kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88041697cc08
Jun 22 17:33:25 terminus kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88041697cc0c
Jun 22 17:33:25 terminus kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88041697cc10
Jun 22 17:33:25 terminus kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc900060b5a18
Jun 22 17:33:25 terminus kernel: [drm] ring test on 0 succeeded in 2 usecs
Jun 22 17:33:25 terminus kernel: [drm] ring test on 1 succeeded in 1 usecs
Jun 22 17:33:25 terminus kernel: [drm] ring test on 2 succeeded in 1 usecs
Jun 22 17:33:25 terminus kernel: [drm] ring test on 3 succeeded in 3 usecs
Jun 22 17:33:25 terminus kernel: [drm] ring test on 4 succeeded in 3 usecs
Jun 22 17:33:25 terminus kernel: [drm] ring test on 5 succeeded in 2 usecs
Jun 22 17:33:25 terminus kernel: [drm] UVD initialized successfully.
Jun 22 17:33:25 terminus kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Jun 22 17:33:25 terminus kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Jun 22 17:33:25 terminus kernel: [drm] ib test on ring 2 succeeded in 0 usecs                                       
Jun 22 17:33:25 terminus kernel: [drm] ib test on ring 3 succeeded in 0 usecs                                       
Jun 22 17:33:25 terminus kernel: [drm] ib test on ring 4 succeeded in 0 usecs                                       
Jun 22 17:33:26 terminus kernel: [drm] ib test on ring 5 succeeded

The strange thing is that the "xrandr --listproviders" shows radeon provider twice:

Providers: number : 3
Provider 0: id: 0x7e cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 8 associated providers: 2 name:Intel
Provider 1: id: 0x52 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 1 associated providers: 2 name:radeon
Provider 2: id: 0x52 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 1 associated providers: 2 name:radeon

Comment 1 Alex Deucher 2015-06-24 17:56:57 UTC

Please attach your xorg log and dmesg output.

Comment 2 yaroslav.sapozhnik 2015-06-24 17:59:11 UTC

Created attachment 180861 [details]
dmesg

Comment 3 yaroslav.sapozhnik 2015-06-24 17:59:28 UTC

Created attachment 180871 [details]
Xorg log

Comment 4 yaroslav.sapozhnik 2015-07-13 14:25:44 UTC

The issue is still there after update to 4.0.7.

Comment 5 yaroslav.sapozhnik 2015-08-04 14:30:02 UTC

Still there with kernel 4.1.3-200.fc22.x86_64

Comment 6 yaroslav.sapozhnik 2015-09-14 18:18:44 UTC

Seems like it's fixed with 4.1.6-200.fc22.x86_64. I'll monitor this for some time.