Dear Ville Syrjälä, Thank you for responding so quickly. I was occupied with work and life for the past two weeks, sorry about the wait, but have now managed to find some time to continue pursuing this issue again. On Thu, 2020-10-01 at 18:23 +0300, Ville Syrjälä wrote: > Argh. If only I had managed to land the full dbuf rework and nuke > this mess before it came back to bite us... Yeah... I know the feeling. > This is definitely going to break something else, so not great. I did expect that. The automated tests failing was a pretty good indicator. You put that code in to take care of something. All I did was just tear it down because it happens to work better for me... blunt but functional for my purposes. Seems to need some finesse or a condition to not cause my problem? Yet still function for the reason you put it in there for. I am more than willing to play guinea pig and test patches on my end to improve it with you. > Can you file an upstream bug at > https://gitlab.freedesktop.org/drm/intel/issues/new > and attach dmesgs from booting both good and bad kernels with > drm.debug=0x1e passed to the kernel cmdline? Bump log_buf_len= > if necessary to capture the full log. I have done so today. It's at: https://gitlab.freedesktop.org/drm/intel/-/issues/2579 -- Stefan Joosten AT Computing BV Sharing and growing together Tel +31 24 352 72 82 Arnhemsestraatweg 33 info@xxxxxxxxxxxxxx 6881 ND Velp www.atcomputing.nl
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
