On testing linux 4.5-rc( 1 and 2) I have found that my display is not rendered correctly on starting the X server. My screen is mainly black with portions of the desktop appearing from time to time. I have tried the kernel on two different machine with different Radeon cards and the result is the same. The system is a recent LFS build and I use fvwm as my window manager. I will forward xorg.conf and Xorg.0.log files from my testing.
Created attachment 121510 [details] Xorg.0.log XServer log file.
Created attachment 121511 [details] xorg.conf My xorg.conf file from /etc/X11
If this is a regression, can you bisect? Please also attach your dmesg output.
Created attachment 121526 [details] dmesg output dmesg output as requested, I will bisect as suggested. Thanks
Looks like you forced dpm on. Had you been using that previously?
(In reply to Alex Deucher from comment #5) > Looks like you forced dpm on. Had you been using that previously? Yes I have been using this setting for some time, I cannot remember how long (some years ?) or why I set it in the first place.
(In reply to SMF from comment #6) > (In reply to Alex Deucher from comment #5) > > Looks like you forced dpm on. Had you been using that previously? > > Yes I have been using this setting for some time, I cannot remember how long > (some years ?) or why I set it in the first place. The other machine I have tested uses a Turks PRO [Radeon HD 6570/7570/8550] with the same boot settings and fails in the same way.
(In reply to SMF from comment #7) > (In reply to SMF from comment #6) > > (In reply to Alex Deucher from comment #5) > > > Looks like you forced dpm on. Had you been using that previously? > > > > Yes I have been using this setting for some time, I cannot remember how long > > (some years ?) or why I set it in the first place. > > The other machine I have tested uses a Turks PRO [Radeon HD 6570/7570/8550] > with the same boot settings and fails in the same way. Looking back over my bug history I found this activity: https://bugzilla.kernel.org/show_bug.cgi?id=60857
Result of bisect: 01c8f1c44b83a0825b573e7c723b033cece37b86 is the first bad commit commit 01c8f1c44b83a0825b573e7c723b033cece37b86 Author: Dan Williams <dan.j.williams@intel.com> Date: Fri Jan 15 16:56:40 2016 -0800 mm, dax, gpu: convert vm_insert_mixed to pfn_t Convert the raw unsigned long 'pfn' argument to pfn_t for the purpose of evaluating the PFN_MAP and PFN_DEV flags. When both are set it triggers _PAGE_DEVMAP to be set in the resulting pte. There are no functional changes to the gpu drivers as a result of this conversion. Signed-off-by: Dan Williams <dan.j.williams@intel.com> Cc: Dave Hansen <dave@sr71.net> Cc: David Airlie <airlied@linux.ie> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> :040000 040000 dc71b6dc188dea4b6ce95f5fd1e4e73cc3663cbe 8a745459a14cd2a6f4e1c71fda3e54333d023f43 M arch :040000 040000 9e8103b65698f677e17becdac53914ca029a6197 f656e15bffef4ea8c848176a79eb50a071ec323e M drivers :040000 040000 3ffc222d7e0f1067772798d08777aeb54136026e e2b423f85aaaf0cb25d48d1e15771fc5bddf7981 M fs :040000 040000 392d2dea8185ba8f0d1c101782831ceed9aa9812 9e3001b04052daa1b3204b6f2a6e26138a4ed7dd M include :040000 040000 f81d8cfe3052b7259b75a58656a65efdaad40284 969d0ff262020f27a695172ce89ae5f6088e8d44 M mm
(In reply to SMF from comment #9) > 01c8f1c44b83a0825b573e7c723b033cece37b86 is the first bad commit > commit 01c8f1c44b83a0825b573e7c723b033cece37b86 > Author: Dan Williams <dan.j.williams@intel.com> [...] > There are no functional changes to the gpu drivers as a result of this > conversion. Famous last words. :) Please report this to Dan Williams.
relevant threads: http://lists.freedesktop.org/archives/dri-devel/2016-January/099471.html http://lists.freedesktop.org/archives/dri-devel/2016-January/099511.html
Thanks Alex. Resolving as not a driver bug.
Tested the patch given here with linux-4.5-rc2 and it did NOT fix the problem for me: http://lists.freedesktop.org/archives/dri-devel/2016-January/099511.html
That's unfortunate, but doesn't change that it's probably not a driver bug and that you should get in touch with Dan Williams about it.
(In reply to Michel Dänzer from comment #14) > That's unfortunate, but doesn't change that it's probably not a driver bug > and that you should get in touch with Dan Williams about it. Thanks just e-mailed him.
(In reply to SMF from comment #15) > (In reply to Michel Dänzer from comment #14) > > That's unfortunate, but doesn't change that it's probably not a driver bug > > and that you should get in touch with Dan Williams about it. > > Thanks just e-mailed him. Solution found see: https://bugzilla.kernel.org/show_bug.cgi?id=112211 For details.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.