From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 18:58:09 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 B306216A41A; Tue, 30 Oct 2007 18:58:09 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 156CA13C4A5; Tue, 30 Oct 2007 18:58:08 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47277EC4.4030003@FreeBSD.org> Date: Tue, 30 Oct 2007 19:58:12 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "Ralf S. Engelschall" References: <20071029110204.GA64046@engelschall.com> In-Reply-To: <20071029110204.GA64046@engelschall.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: "sigreturn: eflags = 0x80283" after medium-to-high load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 18:58:09 -0000 Ralf S. Engelschall wrote: > 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. Sounds like you need to do some debugging with DDB to identify the system state when it hangs. Kris