Re: Suspend lockup: How to bisect d-r-t specific commits?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



W dniu 27 lipca 2010 17:27 użytkownik Alex Deucher
<alexdeucher@xxxxxxxxx> napisał:
> I'm an idiot.  The sampler state needs to be there as it's not emitted
> subsequently;  I was thinking it got emitted with the texture fetch
> constants like it does in the ddx.  That was the issue all along.
> Thanks for tracking that down.  New set of patches:
> http://people.freedesktop.org/~agd5f/reduce_emit/

Following refers to patches from 	27-Jul-2010 08:26.

After applying all 7 patches I get hard lockup on suspend (not even
resume!). I decided to apply one by one to track this down.

Applying 0001 and 0002 doesn't cause any problem.

After applying 0003 (on top of 0001 and 0002) I get hard lockup just
like in case of all patches. Attached patch shows which part of 0003
has to be reverted to make suspending (and resuming) work. I think
it's still not minimal patch (maybe reverting just part of that code
would be enough) but hope it's small enough to give you some idea.

-- 
Rafał

Attachment: 0003.partial.revert.patch
Description: Binary data

_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux