Comment # 21
on bug 105760
from Thomas Martitz
Created attachment 140560 [details] [review] workaround The attached workaround makes resuming generally work on my system. The problem seems to be that the memory that smu_data->header is pointing to changes behind the code's back. (I used printk inside smu7_populate_single_firmware_entry() and saw that the pointer (&toc->entry[0]) passed to it is widely different from what the caller sees, so I think the structure pointed to by toc gets overwritten) I assume this is some mapped memory and some HW component in the GPU writes to it while the CPU is using it, isn't it? If so, the proper fix would be to prevent that but I don't know what's the proper way of doing it in this context. I hope the experts can take a look into the patch for more insight and a real fix.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
