Bug#538158: Still a problem as of 5.0.3
Ben Hutchings <ben@decadent.org.uk> writes:
> If it's a lot of trouble for you to do that then perhaps it's not worth
> doing until we've investigated a bit further.
I have outfitted our test server with 8GB of memory. I'm going to let
it sit idle with 2.6.26-2-686-bigmem just to see whether it shows the
stuck CPU syndrome. If it does, I'll install 2.6.30 from squeeze.
> Can you tell me anything about the workload of these systems, e.g. are
> they running an NFS server, database server, web server...? Do they
> have heavy disk I/O, network I/O, task load or swap usage?
The two machines are general purpose compute servers and NX servers.
People log in to run their KDE desktop and do whatever it is that they
need to do. The machines are big NFS clients, but they run no special
services. Local disk activity is minimal, and with 28GB of RAM the
swap has never been used so far. So, network activity is higher than
a typical workstation, but the average sustained rate is not that
high. There usually are over a thousand concurrent processes running.
> In fact, after further investigation, it looks quite plausible that this
> bug is related to long idle periods. I found some bug fixes made in
> Linux 2.6.27 that may address this.
This would make sense, because, we saw more of this bug before we
announced the servers to our users, and they (the servers) just sat
idle.
Thanks,
--
Arcady Genkin : CDF Systems Administrator
http://www.cdf.toronto.edu/~agenkin/
Reply to: