From owner-freebsd-alpha@FreeBSD.ORG Sat Nov 15 04:32:57 2003 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73A7316A4CE; Sat, 15 Nov 2003 04:32:57 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id B503B43FA3; Sat, 15 Nov 2003 04:32:56 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0C69566D35; Sat, 15 Nov 2003 04:32:56 -0800 (PST) Date: Sat, 15 Nov 2003 04:32:55 -0800 From: Kris Kennaway To: alpha@FreeBSD.org, jeff@FreeBSD.org Message-ID: <20031115123255.GA96854@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Alpha lockups with statfs changes X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2003 12:32:57 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline FYI, I accidentally ran a post-statfs alpha world inside a chroot on the August-ish 5.1-C alpha machines, and it caused half of them to lock up (no break to debugger possible from serial console, no console messages - including the signal 12s that I'd expect to be there from the binaries running inside the chroot). It looks like they locked up with the first incompatible binary they ran, instead of dying with signal 12 - or perhaps they ran a binary that did not use the new syscall, but did something else to cause the lockup. The machines that didn't lock up have lots of sig12s on the console, but they also became unresponsive for an hour or so while this was going on (my heartbeat monitoring script could not connect to any of the cluster machines, although half of them eventually started allowing ssh connections again). Kris --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/thz3Wry0BWjoQKURAvC/AKC+/6aAOw65FSPGjSUW2norhYBcxACgtRjd UvdktNKJxnD+L3zz0oHUvms= =NVyH -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--