[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2019-11-19 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

Martin Peres  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #50 from Martin Peres  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/649.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2017-04-19 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #49 from russianneuroman...@ya.ru ---
By the way, seems like issue is much easier to reproduce with Steam desktop
notifications. Try to download something small, and it will show "download
completed" notification, or ask someone to send message to you via integrated
chat. From my latest three freezes I see that few (usually two-three)
notifications should be enough to reproduce this freeze.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2017-04-19 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #48 from russianneuroman...@ya.ru ---
Issue is still reproducible with Linux 4.11rc7 and Mesa 17.2-git.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-12-17 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #47 from russianneuromancer at ya.ru ---
> FWIW, there's no need to set DRI_PRIME for steam itself, it can be set in 
> Properties -> Launch Options of individual games.
Then I have to don't forget to set it for every game. Set it for Steam once is
easier.

> Does the problem still occur with a current kernel?
Due to few issues with Linux 4.9 (not related to graphics) I tested this with
Linux 4.8 and Mesa 13.0.2. Yes, issue is still reproducible.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-11-30 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #46 from Michel Dänzer  ---
FWIW, there's no need to set DRI_PRIME for steam itself, it can be set in
Properties -> Launch Options of individual games.

Does the problem still occur with a current kernel?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-05-12 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #45 from Mez  ---
Indeed, this works, but at the cost of a 33% decrease in performance, meaning
that my discrete GPU actually renders games as well as my integrated GPU.
Hence, I deactivated this option to start Steam. I'd rather have freezes (I can
avoid without going into context menus) than play games in a choppy way.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-05-12 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #44 from russianneuromancer at ya.ru ---
Maz, I launch Steam like this "LIBGL_DRI3_DISABLE=1 DRI_PRIME=1 steam" as
workaround for now.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-05-11 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #43 from Mez  ---
I also have those freezes in the Steam context menu when using DRI3 and
DRI_PRIME=1 to start Steam. Never with the integrated GPU or with fglrx.

I have a muxless AMD/AMD hybrid 6480G/6650M setup, I'm running Ubuntu
16.04/Unity on kernel 4.6-rc6 with radeon.runpm=0 set as boot (DRI_PRIME
doesn't work with dpm enabled for me), and this happens with mesa 11.2 and
11.3-devel (oibaf or padoka ppa).

I must add that I can play games perfectly without any freezes, it's just when
navigating in Steam context menus or settings that I encounter this, and the
system is unresponsive, no Ctrl-alt-fx to tty or such.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-28 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #42 from Vladislav Kamenev  ---
(In reply to Michel D�nzer from comment #41)
> (In reply to Vladislav Kamenev from comment #40)
> > cannot encounter freeze while using kernel with ZEN patches.
> 
> What patches are those?

https://liquorix.net/
And i run into one or two freezes during these three days.
And now it looks like nature of my freezes differs from OP's one, despite
having 6650m like him.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-27 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #41 from Michel D�nzer  ---
(In reply to Vladislav Kamenev from comment #40)
> cannot encounter freeze while using kernel with ZEN patches.

What patches are those?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-25 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #40 from Vladislav Kamenev  ---
cannot encounter freeze while using kernel with ZEN patches.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-19 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #39 from russianneuromancer at ya.ru ---
So you get hang with DRI2 too?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-18 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #38 from Vladislav Kamenev  ---
Last my comments is false.
It somehow depends on the resolution of running application.
When i was windowed and in 640x480 - all was OK
but when i switched to windowed in 1280x1024(currently my fullscreen) - kernel
hangup

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-18 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #37 from Vladislav Kamenev  ---
Update
When internal GPU is on DRI3 and Radeon Hd6550m on DRI2 - no hangup is present.
Looks like a temporary possible workaround.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-07 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #36 from Vladislav Kamenev  ---
(In reply to russianneuromancer from comment #35)
> So freeze occur when i915 driver is used for iGPU and fglrx is used for
> dGPU? Without radeon driver, right?

Yup.
Looks like its not a r600 problem but a kernel one.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-07 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #35 from russianneuromancer at ya.ru ---
So freeze occur when i915 driver is used for iGPU and fglrx is used for dGPU?
Without radeon driver, right?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-07 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #34 from Vladislav Kamenev  ---
Freezes is present on 4.2 kernel with 15.9 fglrx-updates driver.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-07 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #33 from Vladislav Kamenev  ---
Couldn't run any application on 4.6-rc2.
Freezes still occurs on 4.5 kernel with latest xorg 1.18.3

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-04-07 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #32 from Vladislav Kamenev  ---
On new 4.6.0-rc2 kernel with latest 1.18.3 xorg and 11.2.0 mesa
[  757.856679] radeon :01:00.0: ring 0 stalled for more than 10416msec
[  757.856684] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  758.356670] radeon :01:00.0: ring 0 stalled for more than 10916msec
[  758.356675] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  758.856748] radeon :01:00.0: ring 0 stalled for more than 11416msec
[  758.856764] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  759.356758] radeon :01:00.0: ring 0 stalled for more than 11916msec
[  759.356766] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  759.856744] radeon :01:00.0: ring 0 stalled for more than 12416msec
[  759.856755] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  760.356648] radeon :01:00.0: ring 0 stalled for more than 12916msec
[  760.356660] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  760.856619] radeon :01:00.0: ring 0 stalled for more than 13416msec
[  760.856627] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  761.356588] radeon :01:00.0: ring 0 stalled for more than 13916msec
[  761.356592] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  761.856589] radeon :01:00.0: ring 0 stalled for more than 14416msec
[  761.856594] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  762.356645] radeon :01:00.0: ring 0 stalled for more than 14916msec
[  762.356656] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  762.856662] radeon :01:00.0: ring 0 stalled for more than 15416msec
[  762.856675] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  763.356583] radeon :01:00.0: ring 0 stalled for more than 15916msec
[  763.356593] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  763.856677] radeon :01:00.0: ring 0 stalled for more than 16416msec
[  763.856689] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  764.356567] radeon :01:00.0: ring 0 stalled for more than 16916msec
[  764.356576] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  764.856528] radeon :01:00.0: ring 0 stalled for more than 17416msec
[  764.856532] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  765.356726] radeon :01:00.0: ring 0 stalled for more than 17916msec
[  765.356738] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  765.857224] radeon :01:00.0: ring 0 stalled for more than 18416msec
[  765.857245] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  766.357936] radeon :01:00.0: ring 0 stalled for more than 18916msec
[  766.357946] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  766.858702] radeon :01:00.0: ring 0 stalled for more than 19416msec
[  766.858713] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  767.359323] radeon :01:00.0: ring 0 stalled for more than 19916msec
[  767.359328] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  767.860120] radeon :01:00.0: ring 0 stalled for more than 20416msec
[  767.860131] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  768.360817] radeon :01:00.0: ring 0 stalled for more than 20916msec
[  768.360829] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  768.861474] radeon :01:00.0: ring 0 stalled for more than 21416msec
[  768.861482] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence id 0x023f on ring 0)
[  769.362132] radeon :01:00.0: ring 0 stalled for more than 21916msec
[  769.362137] radeon :01:00.0: GPU lockup (current fence id
0x022d last fence

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-31 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

Vladislav Kamenev  changed:

   What|Removed |Added

 Attachment #122639|0   |1
is obsolete||

--- Comment #31 from Vladislav Kamenev  ---
Created attachment 122647
  --> https://bugs.freedesktop.org/attachment.cgi?id=122647&action=edit
Binary kernel log on freeze.

Don't use anything but cat to watch it.
I copied some string on my last comment.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-31 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #30 from Vladislav Kamenev  ---
(In reply to russianneuromancer from comment #29)
> > Now i use NFS:Underground to cause freezes.
> > Have been playing for hours
> Vladislav, NFS doesn't cause freezes for you this time? Or you played
> different game?

I got an update. 
WoW causes freezes. NFS causes them too.
I was so stupid and watched kern.log in "mousepad"
But when i cat'ted it
received this
Mar 29 19:38:55 xubuntu-beta kernel: [16936.700521] radeon :01:00.0: ring 0
stalled for more than 27944msec
Mar 29 19:38:55 xubuntu-beta kernel: [16936.700526] radeon :01:00.0: GPU
lockup (current fence id 0x00254b78 last fence id 0x00254b82 on
ring 0)
Mar 29 19:38:55 xubuntu-beta kernel: [16937.200516] radeon :01:00.0: ring 0
stalled for more than 28444msec
Mar 29 19:38:55 xubuntu-beta kernel: [16937.200521] radeon :01:00.0: GPU
lockup (current fence id 0x00254b78 last fence id 0x00254b82 on
ring 0)
Mar 29 19:38:56 xubuntu-beta kernel: [16937.700535] radeon :01:00.0: ring 0
stalled for more than 28944msec
Mar 29 19:38:56 xubuntu-beta kernel: [16937.700540] radeon :01:00.0: GPU
lockup (current fence id 0x00254b78 last fence id 0x00254b82 on
ring 0)
Mar 29 19:38:56 xubuntu-beta kernel: [16938.200522] radeon :01:00.0: ring 0
stalled for more than 29444msec
Mar 29 19:38:56 xubuntu-beta kernel: [16938.200527] radeon :01:00.0: GPU
lockup (current fence id 0x00254b78 last fence id 0x00254b82 on
ring 0)
Mar 29 19:38:57 xubuntu-beta kernel: [16938.700546] radeon :01:00.0: ring 0
stalled for more than 29944msec
Mar 29 19:38:57 xubuntu-beta kernel: [16938.700551] radeon :01:00.0: GPU
lockup (current fence id 0x00254b78 last fence id 0x00254b82 on
ring 0)
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087654] radeon :01:00.0: Saved
156391 dwords of commands on ring 0.
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087703] radeon :01:00.0: GPU
softreset: 0x0008
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087706] radeon :01:00.0:  
GRBM_STATUS   = 0xA828
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087708] radeon :01:00.0:  
GRBM_STATUS_SE0   = 0x0001
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087710] radeon :01:00.0:  
GRBM_STATUS_SE1   = 0x0007
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087713] radeon :01:00.0:  
SRBM_STATUS   = 0x26C0
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087715] radeon :01:00.0:  
SRBM_STATUS2  = 0x
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087718] radeon :01:00.0:  
R_008674_CP_STALLED_STAT1 = 0x
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087720] radeon :01:00.0:  
R_008678_CP_STALLED_STAT2 = 0x00010002
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087723] radeon :01:00.0:  
R_00867C_CP_BUSY_STAT = 0x00020182
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087725] radeon :01:00.0:  
R_008680_CP_STAT  = 0x80038243
Mar 29 19:38:57 xubuntu-beta kernel: [16939.087728] radeon :01:00.0:  
R_00D034_DMA_STATUS_REG   = 0x44C83D57
Mar 29 19:38:57 xubuntu-beta kernel: [16939.489275] radeon :01:00.0: Wait
for MC idle timedout !
Mar 29 19:38:57 xubuntu-beta kernel: [16939.489280] radeon :01:00.0:
GRBM_SOFT_RESET=0x4001
Mar 29 19:38:57 xubuntu-beta kernel: [16939.489334] radeon :01:00.0:
SRBM_SOFT_RESET=0x0100
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490485] radeon :01:00.0:  
GRBM_STATUS   = 0x0828
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490488] radeon :01:00.0:  
GRBM_STATUS_SE0   = 0x0001
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490490] radeon :01:00.0:  
GRBM_STATUS_SE1   = 0x0007
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490492] radeon :01:00.0:  
SRBM_STATUS   = 0x26C0
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490495] radeon :01:00.0:  
SRBM_STATUS2  = 0x
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490497] radeon :01:00.0:  
R_008674_CP_STALLED_STAT1 = 0x
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490499] radeon :01:00.0:  
R_008678_CP_STALLED_STAT2 = 0x
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490502] radeon :01:00.0:  
R_00867C_CP_BUSY_STAT = 0x
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490504] radeon :01:00.0:  
R_008680_CP_STAT  = 0x
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490507] radeon :01:00.0:  
R_00D034_DMA_STATUS_REG   = 0x44C83D57
Mar 29 19:38:57 xubuntu-beta kernel: [16939.490535] radeon :01:00.0: GPU
reset succeeded, trying to resume
Mar 29 19:38:57 xubuntu-beta kernel: [16939.497589] [drm] PCIE gen 2 link
speeds already enabled
Mar 29 19:38:58 xubuntu-beta kernel: [16939.901498] radeon :01:00.0: Wait
for MC idle timedout !
Mar 29 19:38:58 xubuntu-beta kernel: [16940.10

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-31 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #29 from russianneuromancer at ya.ru ---
> Now i use NFS:Underground to cause freezes.
> Have been playing for hours
Vladislav, NFS doesn't cause freezes for you this time? Or you played different
game?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-31 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #28 from Vladislav Kamenev  ---
Have been playing for hours and got only 
[62667.941234] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure
on pipe B (start=3758680 end=3758681) time 206 us, min 1017, max 1023, scanline
start 1010, end 1022

error in dmesg.
Using patched kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-31 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #27 from Maarten Lankhorst  ---
Indeed, this is not a fix. It only keeps the fence alive during wait.

Very likely radeon has a double free somewhere. :(

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-31 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #26 from Michel D�nzer  ---
I think the patch was only intended as a means to get more information, not as
a fix to be merged. Right, Maarten? Did you get more information from the
feedback on the patch so far, or what specifically do you need?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-30 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #25 from Vladislav Kamenev  ---
p.s forgot to mention - after patch freezes in WoW dissappeared. Now i use
NFS:Underground to cause freezes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-30 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #24 from Vladislav Kamenev  ---
(In reply to Michel D�nzer from comment #19)
> (In reply to Vladislav Kamenev from comment #18)
> > Checked a 4.5.0 kernel with this patch.
> > No changes. Suffering kernel freezes.
> 
> Please attach the corresponding dmesg output.


Posted my netconsole log.
Its just nothing.
Runned patched kernel with debug and loglevel=7 kernel parametres.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-30 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #23 from Vladislav Kamenev  ---
Created attachment 122639
  --> https://bugs.freedesktop.org/attachment.cgi?id=122639&action=edit
netconsole log

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-30 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #22 from russianneuromancer at ya.ru ---
I also want to clarify that I not 100% sure because with for example with 4.1.6
this issue takes two days of uptime and some usage to get reproduced (comment
#6).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-30 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #21 from Vladislav Kamenev  ---
(In reply to Michel D�nzer from comment #19)
> (In reply to Vladislav Kamenev from comment #18)
> > Checked a 4.5.0 kernel with this patch.
> > No changes. Suffering kernel freezes.
> 
> Please attach the corresponding dmesg output.

Cannot make any logs cuz of freeze.
Will try netconsole again today.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-30 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #20 from russianneuromancer at ya.ru ---
I wasn't able to reproduce issue with patch from Comment #10 (called menu like
two hundred times).

I not sure if it's 100% fixed with this patch, because that was fresh boot, no
other usual programs running, but without this patch issues was reproducible
even under this simple conditions.

So, for now patch seems like help, if crash happen again under different
condition (with longer uptime and more background processes) I will provide new
dmesg.

Michel, please let me know do you intend to submit this patch to upstream?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-30 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #19 from Michel D�nzer  ---
(In reply to Vladislav Kamenev from comment #18)
> Checked a 4.5.0 kernel with this patch.
> No changes. Suffering kernel freezes.

Please attach the corresponding dmesg output.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-29 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

Vladislav Kamenev  changed:

   What|Removed |Added

 Blocks||94667

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-29 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #18 from Vladislav Kamenev  ---
(In reply to Maarten Lankhorst from comment #10)
> Created attachment 119927 [details] [review]
> Use reservation_object_wait_timeout_rcu
> 
> I have no idea what can go wrong, lets find out if adding refcounts during
> wait helps..
> 
> Could you check the output with this patch? ^

Checked a 4.5.0 kernel with this patch.
No changes. Suffering kernel freezes. I built package and sent to OP to help
him make some logs of this.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-28 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #17 from Vladislav Kamenev  ---
Also affects me. 
Intel HD3000 + AMD Radeon HD 6550m.
Easy way to reproduce.
Launch anygame in wine with DRI_PRIME=1
I tried WoW and NFS:Underground.
Freeze happen in 2-3 seconds in NFS and 10-15 minutes in WoW
Kdump - no record.
Netconsole - empty output.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-28 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

Vladislav Kamenev  changed:

   What|Removed |Added

   See Also||https://bugs.freedesktop.or
   ||g/show_bug.cgi?id=94667

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-03-27 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #16 from russianneuromancer at ya.ru ---
Still reproducible with 4.6rc1.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-02-10 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #15 from russianneuromancer at ya.ru ---
Title changed per comment #6

Still reproducible, on Linux 4.4 too.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:

[Bug 92258] [regression] Opening menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

2016-02-10 Thread bugzilla-dae...@freedesktop.org 
https://bugs.freedesktop.org/show_bug.cgi?id=92258

russianneuromancer at ya.ru changed:

   What|Removed |Added

Summary|[regression] Opening|[regression] Opening menu
   |context menu in Steam   |in Steam running via
   |running via DRI_PRIME with  |DRI_PRIME with enabled DRI3
   |enabled DRI3 could lead to  |could lead to radeon kernel
   |radeon kernel module crash  |module crash

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: