<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - X server 1.19.3 failure with amdgpu (radeon M295X) on Ubuntu HWE16.04 kernel 4.10.0-28" href="https://bugs.freedesktop.org/show_bug.cgi?id=101998#c36">Comment # 36</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - X server 1.19.3 failure with amdgpu (radeon M295X) on Ubuntu HWE16.04 kernel 4.10.0-28" href="https://bugs.freedesktop.org/show_bug.cgi?id=101998">bug 101998</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to Meik Neubauer from <a href="show_bug.cgi?id=101998#c35">comment #35</a>) > [...] from what I can get out of gdb is that the call stack is pretty clear > [...] Right, which is why I'm saying we don't need more backtraces right now. > The question is, which routine is responsible for setting up the structure in > ent->slave_dst->drawable.pScreen and why is that not done correctly. As I said in <a href="show_bug.cgi?id=101998#c15">comment 15</a>, the question is how ppriv->notify_on_damage ends up being TRUE in ms_dirty_update. The only way I can see that being the case is if msRequestSharedPixmapNotifyDamage was called before, but xf86-video-amdgpu doesn't have any code calling the RequestSharedPixmapNotifyDamage hook. > > We really need answers to the questions in <a href="show_bug.cgi?id=101998#c27">comment 27</a>. > > I cannot set up a second machine. Due to network security restrictions here > I cannot connect between two PCs. And I do not have an external monitor in > any other location. So running a remote gdb debugging session is out of > reach. None of the questions in <a href="show_bug.cgi?id=101998#c27">comment 27</a> are related to remote access or gdb.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>