I am not running any window manager. On the system where I've observed the problems, I have modified xinitrc to simply run the Citrix ICA client instead of a window manager.
If nobody logs into Citrix, there's a server side timeout which causes the Citrix client to exit after ~5 minutes. When Citrix exits, X exits (normally, I believe). I have X setup as the default run-level in inittab, so after a few seconds, X starts again, Citrix is invoked, and the process repeats. After ~12 iterations, the machine slows to a crawl. By 15 or so, it is essentially locked up. This takes about half an hour. To accelerate the process while testing numerous different setting tweaks, I can also reproduce the problem by startinging X manually and hitting ctrl-alt-bkspc as soon as the Citrix client starts. I don't believe that Citrix is the cause, and the system is quite bare otherwise. However, this probably isn't exactly a very common setup. I'll run tests in the configuration you suggested and report back when I have access to these systems tomorrow or Tuesday. thanks again, -pat On Saturday 08 February 2003 05:41 pm, David Dawes wrote: > On Sat, Feb 08, 2003 at 01:07:25PM -0700, patrick charles wrote: > >How would I communicate this? Somebody on XFree86 working with or have > > contact with the appropriate people in kernel/agpgart development? > > First of all, how are you "killing" the X server? I haven't seen this > behaviour when the X server exits normally, and I've done a lot of > testing where 32MB is allocated per run on machines with only 128MB of > physical memory. > > There are people here familiar with the kernel agpgart driver. > > Note that just because top shows that there's little memory free doesn't > mean that the agpgart driver isn't freeing it. Also the agpgart driver > allocates physical pages, never swap. I'm not sure what the symptoms > are when it can't get any free physical pages. On my test system the > free memory indicated by top does go up when the X server exits, and > this is on an otherwise idle system. > > So, I'd suggest starting a bare X server (run just 'X') on an otherwise > idle system, see what top reports, then exit it cleanly > (<Ctrl><Alt><Backspace>), and see if the free memory amount changes. > Check the X server log to confirm how much memory was allocated via the > agpgart mechanism (look for the lines containing "Allocated"). > > If that looks OK, then try the same thing you tried before but with a bare > X server and an idle system. > > David _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
