Hi Michel, I double checked and you are right, the change 0 -> i works. Cheers Julien On 24 March 2017 at 09:59, Michel Dänzer <michel at daenzer.net> wrote: > On 24/03/17 06:50 PM, Julien Isorce wrote: > > Hi Michel, > > > > (Just for other readers my reply has been delayed on the mailing lists > > and should have been on second position) > > It is on https://patchwork.freedesktop.org/patch/145731/ , did you mean > something else? > > The delay was because you weren't subscribed to the amd-gfx mailing list > yet, so your post went through the moderation queue. > > > > I will have a go with that change and let you know. I do not remember if > > I tried it for this soft lockup. But for sure it does not solve the hard > > lockup that Zach also mentioned at the end of his reply. > > I'll follow up to his post about that. > > > > But in general, isn't "radeon_lockup_timeout" supposed to detect this > > situation ? > > No, it's for detecting GPU hangs, whereas this is a CPU "hang" (infinite > loop). > > > -- > Earthling Michel Dänzer | http://www.amd.com > Libre software enthusiast | Mesa and X developer > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20170324/c1ad166a/attachment.html>
