Re: lock contention problem?

2011-01-14 Thread dieterbsd
It might be a hardware resource starvation problem. It is possible to nice umass by simply adding a line like: .interval = 2,/* 2 milliseconds */ Thanks, but it didn't help. Also tried setting it to 1, 4, and 20. http://svn.freebsd.org/changeset/base/217350 Is

lock contention problem?

2011-01-13 Thread dieterbsd
I suspect that I have a problem with lock/mutex contention. Reading from a USB disk appears to lock out the firewire driver for too long, causing data transfer (writing to firewire bus) to fail with EAGAIN. Once it fails it does not recover. kernel: fwohci1: IT DMA underrun (0x40308011) (stat

Re: lock contention problem?

2011-01-13 Thread Hans Petter Selasky
On Thursday 13 January 2011 21:28:15 dieter...@engineer.com wrote: I suspect that I have a problem with lock/mutex contention. Reading from a USB disk appears to lock out the firewire driver for too long, causing data transfer (writing to firewire bus) to fail with EAGAIN. Once it fails it