On Mon, 29 Apr 1996 10:26:43 +0200 (MET DST), Matthias Sattler
<m_sattle@informatik.uni-kl.de> said:
>> As long as the working set does not change everything is normal, but even
>> the smallest change results in heavy swapping (while the output of free
>> looks normal).
> In fact I don't see the problems with the original ncr driver, so it is
> very likely that the bug is somewhere in the ncrBsd2Linux driver. Is
> there something I can do to find out more about the nature of this problem ?
This looks odd. I'd have said it was a sign of a memory leak in the
driver if it wasn't for the fact that you are sure things are OK if
the working set remains constant. Does this apply even if you keep
working for many hours? Is it really the working set or simply the
uptime which triggers the problem?
Cheers,
Stephen.
-- Stephen Tweedie <sct@dcs.ed.ac.uk> Department of Computer Science, Edinburgh University, Scotland.