<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - drm-next-2018-12-14 -Linux PPC" href="https://bugs.freedesktop.org/show_bug.cgi?id=109345#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - drm-next-2018-12-14 -Linux PPC" href="https://bugs.freedesktop.org/show_bug.cgi?id=109345">bug 109345</a> from <a class="email" href="mailto:chzigotzky@xenosoft.de" title="Christian Zigotzky <chzigotzky@xenosoft.de>"> Christian Zigotzky</a> <pre>(In reply to Alex Deucher from <a href="show_bug.cgi?id=109345#c23">comment #23</a>) > (In reply to Christian Zigotzky from <a href="show_bug.cgi?id=109345#c22">comment #22</a>) > > Again. Did you modify the behaviour of the initialisation of two graphics > > cards in the DRM updates 'drm-next-2018-12-14'? If you say no, then I can > > look in the PowerPC updates. You need to know if there was a change or you > > don't know what you published. It's not the task for the enduser to look in > > your code or bisect the code because you don't know the changes. It is > > always the same. You changed the code and after that we have issues and we > > endusers and first level support have to figure out where the problem is. > > And if we don't figure out the issue then the issue remains. It's easy to > > write that you don't have this platform. > > No, the only changes were changes in comments, removing some unused code and > changes in the shared ttm module that touched all drivers that use ttm. Thank you for your reply! OK, we know that without the DRM updates 2018-12-14 the 2 graphics cards work together without any problems. With which good and bad commit should I start bisecting? @Allan I have to compile a lot of test kernels but I can’t test them because I don’t have these two graphics cards. Please test all test kernels.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>