search for: gk104_fifo_intr_runlist

Hi, I am testing Linux v4.2-rc5 and I am sporadically getting crashes shortly after startup in gk104_fifo_intr_runlist(). What I've found is that the 'mask' value read from offset 0x2a00 comes back as '0xbad0da00'. This causes the 'engn' variable to be assigned the value 9, which is invalid; then wake_up() is called on an uninitialized waitqueue which causes the crash. Reverting commi...

...ook? 0xbad* generally comes from bad mmio > reads. > > On Aug 9, 2015 1:08 PM, "Eric Biggers" <ebiggers3 at gmail.com> wrote: >> >> Hi, >> >> I am testing Linux v4.2-rc5 and I am sporadically getting crashes shortly >> after >> startup in gk104_fifo_intr_runlist(). What I've found is that the 'mask' >> value >> read from offset 0x2a00 comes back as '0xbad0da00'. This causes the >> 'engn' >> variable to be assigned the value 9, which is invalid; then wake_up() is >> called >> on an uninitiali...

..., 2015 1:08 PM, "Eric Biggers" <ebiggers3 at gmail.com> wrote: >> >> >> >> Hi, >> >> >> >> I am testing Linux v4.2-rc5 and I am sporadically getting crashes >> >> shortly >> >> after >> >> startup in gk104_fifo_intr_runlist(). What I've found is that the >> >> 'mask' >> >> value >> >> read from offset 0x2a00 comes back as '0xbad0da00'. This causes the >> >> 'engn' >> >> variable to be assigned the value 9, which is invalid; then...

This reverts commit 1addc1264852 This commit seems to cause crashes in gk104_fifo_intr_runlist() by returning 0xbad0da00 when register 0x2a00 is read. Since this commit was intended for GM20B which is not completely supported yet, let's revert it for the time being. Reported-by: Eric Biggers <ebiggers3 at gmail.com> Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> -...

This is an initial series of patches to improve channel recovery on Turing GPUs with the goal of improving reliability enough to eventually enable SVM for Turing. It's likely follow up patches will be required to fully address problems with less trivial workloads than what I have been able to test thus far. This series primarily addresses a number of hardware changes to interrupt layout and

On Wed, Aug 12, 2015 at 3:00 PM, Afzal Mohammed <afzal.mohd.ma at gmail.com> wrote: > Hi, > > On Wed, Aug 12, 2015 at 01:17:38PM +0900, Alexandre Courbot wrote: >> This reverts commit 1addc1264852 >> >> This commit seems to cause crashes in gk104_fifo_intr_runlist() by >> returning 0xbad0da00 when register 0x2a00 is read. Since this commit was >> intended for GM20B which is not completely supported yet, let's revert >> it for the time being. >> >> Reported-by: Eric Biggers <ebiggers3 at gmail.com> >> Signed-off-b...

Hi there, Resending these now that they've had some more polish and testing, and I heard that Ben's vacation is over :-) These patches work as a starting point for more explicit error mechanisms and better robustness. At the moment, when a job hangs or faults, it seems that nouveau doesn't quite know how to handle the situation and often results in a hang. Some of these situations