Re: Stuck in "objtrm" - live kernel test to run

1999-07-11 Thread Stephen McKay
On Saturday, 10th July 1999, Matthew Dillon wrote: >I'm trying to simulate your 486 setup. You must love pain! A make -j5 >buildworld on a 16MB-limited machine pages like hell (200-400 pageins/sec >AND 200-400 pageouts/sec simultaniously, almost continuously). Maximal pain, maximal

Re: Stuck in "objtrm" - live kernel test to run

1999-07-09 Thread Matthew Dillon
:Cute. After the ps axlf, all the swapped out processes went from 0 to 8 KB :resident. But the stuck process stayed at 0 KB resident. It wasn't :swapped out anyway, according to the ps flags, so it should have had some :resident pages. Seems like a contradiction to me. : :Stephen. Yah. t

Re: Stuck in "objtrm" - live kernel test to run

1999-07-09 Thread Stephen McKay
On Thursday, 8th July 1999, Matthew Dillon wrote: >There is a way we can find out for sure. For any of you with processes >stuck in objtrm, see if you can gdb the kernel and get a backtrace >of that process to see if it might be in a state where a previous >call context is holdin

Re: Stuck in "objtrm" - live kernel test to run

1999-07-08 Thread Matthew Dillon
Ok, I've traced the code down and I think that there is a good chance that the OBJ_DEAD fix that Alan described may solve the problem. What I think is happening is that a process context is holding a PIP count on the object, then deallocating the object and creating an interlo