Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 May 2010 09:30:05 -0700
From:      Carl Johnson <carlj@peak.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Bash lockups
Message-ID:  <87pr0przea.fsf@cjlinux.localnet>
In-Reply-To: <878w7d7qbb.fsf@kobe.laptop> (Giorgos Keramidas's message of "Fri\, 21 May 2010 08\:54\:16 %2B0300")
References:  <877hmzbi1f.fsf@cjlinux.localnet> <878w7d7qbb.fsf@kobe.laptop>

next in thread | previous in thread | raw e-mail | index | archive | help
Giorgos Keramidas <keramida@ceid.upatras.gr> writes:

> On Wed, 19 May 2010 16:14:52 -0700, Carl Johnson <carlj@peak.org> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87pr0przea.fsf>