From owner-freebsd-current Wed Feb 18 02:05:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29339 for freebsd-current-outgoing; Wed, 18 Feb 1998 02:05:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from p.funk.org (p.funk.org [194.109.61.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29305 for ; Wed, 18 Feb 1998 02:05:06 -0800 (PST) (envelope-from alexlh@p.funk.org) Received: (from alexlh@localhost) by p.funk.org (8.8.8/8.8.8) id LAA00245; Wed, 18 Feb 1998 11:04:00 +0100 (CET) (envelope-from alexlh) Message-ID: <19980218110400.10041@p.funk.org> Date: Wed, 18 Feb 1998 11:04:00 +0100 From: Alex Le Heux To: freebsd-current@FreeBSD.ORG Subject: weird things happening Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, My machine has been experiencing mysterious hangs for the past week. At first I suspected Luigi's new drivers, or the soundcard (as that was the last thing I had modified), but they both turned out to be innocent. Investigation indicated that it would freeze the moment it tried to swap. I emailed to freebsd-current about this, and John Dyson responded saying that there were several patches to the vm system underway. The vm system is way beyond me, so after looking at it for a while I decided to wait for those patches. Today however I noticed something interesting. This might be normal behaviour, if so, I would like to know what causes it. While running without swap, in 48 mb, trying to stress the memory system, I fired up: X, afterstep, two copies of netscape and two copies of wp7 (yuch). The machine slowed down to a crawl. Even moving the mouse from one side of the screen to the other took about 30 seconds. I had top running in an xterm, and it would update that window at the blazing speed of about 2 chars/sec. The load hovered somewhere around 5. After killing one of the netscapes everything returned to normal. During all this there was no disk activity whatsoever. If this is normal behaviour, I'd be interested in knowing what the system is so busy with, and if it's not, someone else might be interested in hearing about this, hence my post. Cheers, Alex -- Hi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message