From owner-freebsd-arm@FreeBSD.ORG  Thu Feb  7 00:59:59 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 467C95BA
 for <freebsd-arm@freebsd.org>; Thu,  7 Feb 2013 00:59:59 +0000 (UTC)
 (envelope-from gonzo@id.bluezbox.com)
Received: from id.bluezbox.com (id.bluezbox.com [88.198.91.248])
 by mx1.freebsd.org (Postfix) with ESMTP id C31D1890
 for <freebsd-arm@freebsd.org>; Thu,  7 Feb 2013 00:59:58 +0000 (UTC)
Received: from [88.198.91.248] (helo=[IPv6:::1])
 by id.bluezbox.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256)
 (Exim 4.77 (FreeBSD)) (envelope-from <gonzo@id.bluezbox.com>)
 id 1U3Fq9-000FqX-Lj
 for freebsd-arm@freebsd.org; Wed, 06 Feb 2013 16:59:51 -0800
Message-ID: <5112FC85.5060704@bluezbox.com>
Date: Wed, 06 Feb 2013 16:59:49 -0800
From: Oleksandr Tymoshenko <gonzo@bluezbox.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: freebsd-arm@freebsd.org
Subject: Re: Hung when execute man
References: <CANuCnH9p7WkUe_-RRRsRTLa8Y6UYnTmBpYXv5a6rkJyUFN-ceg@mail.gmail.com>
In-Reply-To: <CANuCnH9p7WkUe_-RRRsRTLa8Y6UYnTmBpYXv5a6rkJyUFN-ceg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: gonzo@id.bluezbox.com
X-Spam-Level: --
X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com",
 has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 The administrator of that system for details.
 Content preview:  On 2/6/2013 4:30 AM, Alie Tan wrote: > Hi, > > My RasPi hung
 when I execute man man, man ping, etc. > > Any idea how to debug or grab
 error msg for this case? > Does it happen on serial console, ov video console
 or in SSH session? I suggest open two kinds of sessions to check if it's
 really system problem or just one type of console lock up. [...] 
 Content analysis details:   (-2.9 points, 5.0 required)
 pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
 [score: 0.0000]
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 00:59:59 -0000

On 2/6/2013 4:30 AM, Alie Tan wrote:
> Hi,
>
> My RasPi hung when I execute man man, man ping, etc.
>
> Any idea how to debug or grab error msg for this case?
>

Does it happen on serial console, ov video console or in SSH session?
I suggest open two kinds of sessions to check if it's really system problem
or just one type of console lock up.