Try at least stracing pump and find out _which_ operation fails.
Then find out where in the source there are messages "operation
failed" and whatever messages are around that message and compare
these positions with the call trace you get from strace and an
static analysis of the code paths leading to this message.
As a last resort try to run a debugger over pump (you have to
rebuild it without optimization and with debugging symbols).
This sounds like an user space problem until now, but once you
tried all this, we can decide whether it is a kernel bug or a bug
in pump, which got triggered by more correct behavior of the
lastest kernels.
Regards
Ingo Oeser
-- 10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag> <<<<<<<<<<<< been there and had much fun >>>>>>>>>>>> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/