>> Kevin Lahey <kml@patheticgeek.net> writes:

>> Looking at the kernel backtraces that I get when things go wrong,
>> it seems more like a MIPS-specific VM issue than a Tulip driver
>> issue. I agree that it is a problem.

My impression, too! (see
http://mail-index.netbsd.org/port-cobalt/2004/11/04/0000.html )

I've played with cobalt/cobalt/bus.c dcache handling during pci i/o
lst day; I still get corrupted files!

Decreasing sysctl's vm.max{anon,exec,file}max diminishes the problem
for me (but does not solve the problem)... and also goes into VM
direction!

Now, how to find somebody who _can_ investigate this further?

Shouldn't other mips people (e. g. sgimips) see the same problems?

Markus.