summaryrefslogtreecommitdiffstats
path: root/sys/dev/idt
diff options
context:
space:
mode:
authorjhb <jhb@FreeBSD.org>2006-04-28 20:08:16 +0000
committerjhb <jhb@FreeBSD.org>2006-04-28 20:08:16 +0000
commitca65c8d400f4a855b84394629b8695274cf7bfb4 (patch)
treed47bd827c11d10f92040d69f9f335f6cae2c372b /sys/dev/idt
parent4bbacc2510826865e6a74758b30aa79da6cc9f92 (diff)
downloadFreeBSD-src-ca65c8d400f4a855b84394629b8695274cf7bfb4.zip
FreeBSD-src-ca65c8d400f4a855b84394629b8695274cf7bfb4.tar.gz
The nvidia binary blob sometimes defers tx completion notification to the
OS dependent layer. Thus, the watchdog timer can go off when the tx engine is working fine but the OS dependent layer just hasn't been called to cleanup finished tx transactions. To workaround this, when the watchdog fires, poke the binary blob to force it to flush any pending tx completions. If this drops the pending tx count to zero then just return without logging a message or resetting the chip. This reportedly fixes the 'device timeout()' errors with at least several NF4 nve(4) parts. Submitted by: Nathan Alexander Whitehorn <nathanw@uchicago.edu> (code) Submitted by: dg (inspiration for comment and explanation) MFC after: 1 week
Diffstat (limited to 'sys/dev/idt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud