Hi,
I am having problems with a program of mine getting stuck in the vmopar state
when it talks to our custom PCI DA card, and I was wondering if anyone could
give a pointer about where to start looking for problems?
>From my understanding vmopar is where a process is stuck waiting for a page to
become unbusy (which only happens in an interrupt).
This driver didn't have a problem in 2.2.8, so I am not sure if its an OS bug
or mine :)
I looked in the archives and there was a suggestion that it was NFS related so
I umount'd the NFS partitions but no joy.
Any ideas? I really don't want to go back to using 2.2.8+CAM instead of
3.3-RELEASE :)
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
PGP signature
