Quoting Michel Thierry (2017-09-06 16:25:06)
> On 05/09/17 06:57, Chris Wilson wrote:
> > Quoting Chris Wilson (2017-08-21 15:55:34)
> >> Quoting Michel Thierry (2017-08-18 18:23:42)
> >>> The corruption in CSB mmio reads we were seeing has been tracked down to
> >>> incorrectly touching forcewake
On 05/09/17 06:57, Chris Wilson wrote:
Quoting Chris Wilson (2017-08-21 15:55:34)
Quoting Michel Thierry (2017-08-18 18:23:42)
The corruption in CSB mmio reads we were seeing has been tracked down to
incorrectly touching forcewake of all domains, following an engine reset.
It is still a
Quoting Chris Wilson (2017-08-21 15:55:34)
> Quoting Michel Thierry (2017-08-18 18:23:42)
> > The corruption in CSB mmio reads we were seeing has been tracked down to
> > incorrectly touching forcewake of all domains, following an engine reset.
> > It is still a mistery why we only catched this in
Quoting Michel Thierry (2017-08-18 18:23:42)
> The corruption in CSB mmio reads we were seeing has been tracked down to
> incorrectly touching forcewake of all domains, following an engine reset.
> It is still a mistery why we only catched this in Broxton, since it
> could happen in any platform.
The corruption in CSB mmio reads we were seeing has been tracked down to
incorrectly touching forcewake of all domains, following an engine reset.
It is still a mistery why we only catched this in Broxton, since it
could happen in any platform.
With that fix already merged, commit 4055dc75d6b5
