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

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

Michel Dänzer  changed:

   What|Removed |Added

 CC||deathsimple at vodafone.de

--- Comment #14 from Michel Dänzer  ---
(In reply to russianneuromancer from comment #13)
> Michel, Maarten, seems like issue that I reported originally is not same
> issue that polo reporting. For me DRI3 usage cause kernel module crash, for
> him using DRI3 instead of DRI2 is kind of workaround. 
> What you think?

It's probably better if polo files his/her own upstream report then, or sticks
to the downstream one. Since that problem seems to be a regression, it should
be possible to isolate it with git bisect.


(In reply to Maarten Lankhorst from comment #11)
> If this causes a GPF in ttm_bo_wait my guess is radeon has a fence
> refcounting bug, [...]

Indeed, that happened in https://bugs.freedesktop.org/show_bug.cgi?id=93017#c5
. Christian, any ideas where our fence reference counting might be wrong?

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #13 from russianneuromancer at ya.ru ---
Michel, Maarten, seems like issue that I reported originally is not same issue
that polo reporting. For me DRI3 usage cause kernel module crash, for him using
DRI3 instead of DRI2 is kind of workaround. 
What you think?

> Could you check the output with this patch? 
Honestly, I doesn't know how to test it, as I am not developer. But I can test
rc-kernels that available in Ubuntu mainline PPA.

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #12 from polo  ---
how to use this patch? 

I reported this bug on opensuse bugzilla, there's more info
https://bugzilla.opensuse.org/show_bug.cgi?id=954783

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #11 from Maarten Lankhorst  ---
If this causes a GPF in ttm_bo_wait my guess is radeon has a fence refcounting
bug, but if that's the case this patch will cause an infinite loop in
reservation_object_wait_timeout_rcu called from ttm_bo_wait.

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #10 from Maarten Lankhorst  ---
Created attachment 119927
  --> https://bugs.freedesktop.org/attachment.cgi?id=119927=edit
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? ^

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

Michel Dänzer  changed:

   What|Removed |Added

 CC||bugs at mblankhorst.nl

--- Comment #9 from Michel Dänzer  ---
Looks like something goes wrong in ttm_bo_wait. Maarten, any ideas offhand what
could go wrong there, or how to narrow it down?

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #8 from polo  ---
OpenSUSE Leap 42.1  default  DRI2 
A foud  something in Arch wiki,  I But I do not know if it's the same problem.  


Kernel crash/oops when using PRIME and switching windows/workspaces
Note: this has been tested on a system with Intel+AMD
Using DRI3 WITH a config file for the integrated card seems to fix this issue.
To enable DRI3, you need to recompile mesa with --enable-dri3 in the configure
flags[1] and create a config for the integrated card adding the DRI3 option:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "DRI" "3"
EndSection
After this you can use DRI_PRIME=1 WITHOUT having to run xrandr
--setprovideroffloadsink radeon Intel as DRI3 will take care of the offloading.

https://wiki.archlinux.org/index.php/PRIME

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #7 from polo  ---
I have similiar problem on zbook 14 using open driver and DRI_PRIME=1
3.16.7  openSUSE 13.2  work  without any problem
Fedora 21 after  update from 3.18 to 3.19randomly crash using DRI_PRIME=1
4.1.12  openSUSE Leap 42.1  the same issue.

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #6 from russianneuromancer at ya.ru ---
Okay, after two days of uptime I able to reproduce this crash on 4.1.6 too, but
for some reason 4.1.6 require different steps: this time I run Steam in Big
Picture mode, then back to desktop mode, and then call not context menu, but
click on Library button in Steam interface - Library menu appear, and then
system lockup.

Testing 4.1.5 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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

--- Comment #4 from Christian König  ---
The crash looks like the TTM cleanup process tries to free a buffer twice.

Most likely a bug in the reference counting somewhere. Can you try to bisect
the DRM changes between 4.1.6 and 4.1.7?

According to the git logs there wasn't even a single change radeon between
4.1.6 and 4.1.7 so this sounds like a problem in TTM.

-- 
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 context menu in Steam running via DRI_PRIME with enabled DRI3 could lead to radeon kernel module crash

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92258

russianneuromancer at ya.ru changed:

   What|Removed |Added

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

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