Date: Fri, 23 May 2008 22:12:17 -0700 From: "paul beard" <paulbeard@gmail.com> To: "Kris Kennaway" <kris@freebsd.org> Cc: questions@freebsd.org Subject: Re: kernel debugging: seeing swap issues in 7.0 Message-ID: <aeca57d90805232212n93fafcbv10f217e175d06124@mail.gmail.com> In-Reply-To: <20080523210854.GB20868@hub.freebsd.org> References: <aeca57d90805231302h5281f0b0ocb26fb8b0a9250fa@mail.gmail.com> <20080523210854.GB20868@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 23, 2008 at 2:08 PM, Kris Kennaway <kris@freebsd.org> wrote: > > You can try increasing the timeout by editing the relevant kernel > source, but if it's failing to reply to the I/O after 30 seconds then > something is drastically overloaded on your system. Well, not much is running, and I have recently built a new kernel and world in less time than it takes to get this one port upgraded. I think there is something else amiss. Should this really be soaking up 100Mb of RAM? PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 32272 root 1 -20 0 101M 70340K swread 3:04 0.93% cc1 I have filed a bug against gcc, per instructions. There seems to be an issue somewhere in py-gtk that is exacerbated by the low resources on this system. Thanks. -- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aeca57d90805232212n93fafcbv10f217e175d06124>