From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 19:22:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CE8816A475 for ; Mon, 29 Oct 2007 19:22:38 +0000 (UTC) (envelope-from rse@engelschall.com) Received: from visp1.engelschall.com (visp1.engelschall.com [195.30.6.144]) by mx1.freebsd.org (Postfix) with ESMTP id 31C4113C481 for ; Mon, 29 Oct 2007 19:22:36 +0000 (UTC) (envelope-from rse@engelschall.com) Received: by visp1.engelschall.com (Postfix, from userid 21100) id EB7351B44870; Mon, 29 Oct 2007 12:04:16 +0100 (CET) Received: by en1.engelschall.com (Postfix, from userid 10000) id 4C2E36DCCC; Mon, 29 Oct 2007 12:02:04 +0100 (CET) Date: Mon, 29 Oct 2007 12:02:04 +0100 From: "Ralf S. Engelschall" To: freebsd-current@freebsd.org Message-ID: <20071029110204.GA64046@engelschall.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: FreeBSD User-Agent: Mutt/1.5.16 OpenPKG/CURRENT (2007-06-09) Subject: "sigreturn: eflags = 0x80283" after medium-to-high load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ralf S. Engelschall" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 19:22:38 -0000 Just FYI: When I compile lots of C++ code under 8.0 or 7.0 (both as of 2007-10-27 and running on ZFS inside a virtual machine) I'm still able to regularily bring the system into an unusable state. The effect is that first on the console the following kernel messages occur: sigreturn: eflags = 0x80283 sigreturn: eflags = 0x80297 Then after I type e.g. CTRL-C in my C++ compile session over SSH more such "sigreturn: eflags = 0x80283" occur on the console (and without bringing back a shell prompt on the SSH session). At this stage I also no longer can login via SSH through a new second SSH connection. Only on the console I still can perform a "sync; sync; sync; reboot" to rescue. In this situation even a regular "shutdown -r now" often just causes more "sigreturn: eflags = 0x80297" outputs but isn't really able to finally reboot the system. Hmmm... -- rse@FreeBSD.org Ralf S. Engelschall FreeBSD.org/~rse rse@engelschall.com FreeBSD committer www.engelschall.com