The dreaded kernel[0]: NVDA(DMA): Channel timeout! is back, it never was gone anyway

[ncmontas]

It seems that freezefix app workaround cannot stop the issue from happening in El Capitan which cause the system to crashed, using 15A215h El Capitan Public Beta.

 

19/07/2015 12:11:48.634 PM WindowServer[207]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)

19/07/2015 12:11:48.000 PM kernel[0]: NVDA(DMA): Channel timeout!

19/07/2015 12:11:48.000 PM kernel[0]: NVDA: Channel Info: [19, 0x13, 0x10, 0x66a0]

19/07/2015 12:11:48.000 PM kernel[0]: NVDA: Version Info: [com.apple.GeForce, 10.0.6, 0x7d780b0a, 18894120, 310.42.05a49, 1]

 

 

19/07/2015 12:11:49.670 PM DumpGPURestart[948]: Saved gpuRestart report for kernel to /Library/Logs/DiagnosticReports/Kernel_2015-07-19-121149_nathaniels-Mac-Pro.gpuRestart

 

Sun Jul 19 12:11:49 2015

 

Event:               GPU Reset

Data/Time:           Sun Jul 19 12:11:49 2015

Application:         

Path:                

OS Version:          Mac OS X Version 10.11 (Build 15A215h)

Graphics Hardware:   nVidia GeForce GTS 450

Signature:           0

 

Report Data:

 

NVDA(DMA): Channel timeout!

Channel Info: [19, 0x13, 0x10, 0x66a0]

Version Info: [com.apple.GeForce, 10.0.6, 0x7d780b0a, 18894120, 310.42.05a49, 1]

 

 

Currently using an app CUDA-test app that draws multiple triangles in a window, I never like this workaround since it is seen on the desktop. Is other experiencing the issue on their video card?

[fearandleb]

Hi,

 

I experienced this issue quite a lot in combination with my Areca SAS Controller. I have a dual cpu x9dai board and if I use the GFX in a certain pci slot, I get this errors. Sometime they go away by reboot. If I exchange Areca and Nvidia GTX770 Slot, I get Kernel Panics on the ZFS Filesystem.

 

So somehow it is the question on which pci slot the card is installed. Also I recognized this issue related to the Webdriver installed or not, so if the Webdriver is installed, the issue is produced much more often.

 

I do not have any more help at the moment. Also I recognize the issue to be correlated somehow with the ethernetcard, which is on the same PCI Bus, if I have lot of traffic on ethernet, the issue pops up more often...