From owner-freebsd-questions@FreeBSD.ORG Fri May 21 16:30:23 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D580C106567E for ; Fri, 21 May 2010 16:30:23 +0000 (UTC) (envelope-from carlj@peak.org) Received: from redcondor1.peak.org (redcondor1.peak.org [69.59.192.54]) by mx1.freebsd.org (Postfix) with ESMTP id 92B888FC20 for ; Fri, 21 May 2010 16:30:23 +0000 (UTC) Received: from peak-mail-gateway.peak.org ([69.59.192.42]) by redcondor1.peak.org ({e03e86cd-14ae-47ce-9578-3c080ce9c462}) via TCP (outbound) with ESMTP id 20100521163007604 for ; Fri, 21 May 2010 16:30:07 +0000 X-RC-FROM: X-RC-RCPT: Received: from cjlinux.localnet (207.55.91.197.peak.org [207.55.91.197] (may be forged)) (authenticated bits=0) by peak-mail-gateway.peak.org (8.12.10/8.12.8) with ESMTP id o4LGU5u4074169 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 21 May 2010 09:30:06 -0700 (PDT) Received: from carlj by cjlinux.localnet with local (Exim 4.69) (envelope-from ) id 1OFV6r-0006qo-NV for freebsd-questions@freebsd.org; Fri, 21 May 2010 09:30:05 -0700 To: freebsd-questions@freebsd.org References: <877hmzbi1f.fsf@cjlinux.localnet> <878w7d7qbb.fsf@kobe.laptop> From: Carl Johnson Date: Fri, 21 May 2010 09:30:05 -0700 In-Reply-To: <878w7d7qbb.fsf@kobe.laptop> (Giorgos Keramidas's message of "Fri\, 21 May 2010 08\:54\:16 +0300") Message-ID: <87pr0przea.fsf@cjlinux.localnet> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Bash lockups X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2010 16:30:23 -0000 Giorgos Keramidas writes: > On Wed, 19 May 2010 16:14:52 -0700, Carl Johnson wrote: >> I have been experimenting with FreeBSD for a while, and I consistently >> get bash lockups at irregular intervals when it is otherwise idle. By >> lockup, I mean that it stops responding to the keyboard and uses 100% >> CPU. It will sometimes go for days with no problems, but I had two >> yesterday, and other today. They have occurred on test systems >> running in VirtualBox and on a real computer, both i386 and amd64 >> images, and a mixture of 7.1, 7.3 and 8.0. They usually seem to >> happen when I am switching tabs in konsole or switching shells in >> screen, but other times I think they happen when I am not even using >> the system. The only thing I have found I can do is to do a kill -9 >> and start a new shell. > > Does this lock-up happen if you leave the shell 'idle' for too long over > an ssh session? There may be problems with stateful connection tracking > between your terminal and the remote shell :-/ No, I don't think that could be the problem. I am just using ssh between local machines and there is no firewall between them. It also often seems to happen to a shell as I switch away from it to another one. One suspicion is that something is sending a signal to the shell as it switches, and bash sometimes doesn't handle that signal properly. I also should have mentioned that I have been running bash as my default shell for years under Linux and have never seen this problem there. Thanks for the suggestion. -- Carl Johnson carlj@peak.org