From owner-freebsd-current Sun Jul 29 19: 0:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-106-38.dsl.lsan03.pacbell.net [64.169.106.38]) by hub.freebsd.org (Postfix) with ESMTP id 0674037B41B for ; Sun, 29 Jul 2001 19:00:12 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1B5A766B25; Sun, 29 Jul 2001 19:00:11 -0700 (PDT) Date: Sun, 29 Jul 2001 19:00:11 -0700 From: Kris Kennaway To: current@FreeBSD.org Subject: -current lockups Message-ID: <20010729190011.B810@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --uZ3hkaAS1mZxFaxD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, For the past 2 or 3 weeks my -current system has been experiencing temporary lockups, usually under disk load. The entire system will hang for around 20-30 seconds, during which time absolutely no network/IO/keyboard/mouse activity is accepted. Usually, after 20-30 seconds the system will unwedge and activity will resume, but sometimes it hangs forever. There are no console messages logged by this event. I cannot break into DDB until after system activity resumes normally. My system is a PPro 233 using IDE drives. Has anyone else seen something like this? Kris --uZ3hkaAS1mZxFaxD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7ZL+rWry0BWjoQKURAjc0AJ0QlxIjGy/OTrj68O2npLoyJ18JAACeKPiM lBXcCuw6+QhWGliQT1XyeqU= =G9R4 -----END PGP SIGNATURE----- --uZ3hkaAS1mZxFaxD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message