From owner-freebsd-arm@FreeBSD.ORG Tue Feb 12 14:58:51 2013 Return-Path: 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 25163D59 for ; Tue, 12 Feb 2013 14:58:51 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id ECB289A4 for ; Tue, 12 Feb 2013 14:58:50 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r1CEpISd082387 for ; Tue, 12 Feb 2013 07:51:24 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r1CEoeqc041008; Tue, 12 Feb 2013 07:50:55 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: BeagleBone locked up From: Ian Lepore To: Brett Wynkoop In-Reply-To: <20130211204856.713c9ee2@ivory.local> References: <20130210231709.26f122dc@ivory.local> <20130211190606.1c985baf@ivory.local> <1360629932.4545.150.camel@revolution.hippie.lan> <20130211204856.713c9ee2@ivory.local> Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Feb 2013 07:50:40 -0700 Message-ID: <1360680640.4545.157.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Tim Kientzle , freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 14:58:51 -0000 On Mon, 2013-02-11 at 20:48 -0500, Brett Wynkoop wrote: > On Mon, 11 Feb 2013 17:45:32 -0700 > Ian Lepore wrote: > > > On Mon, 2013-02-11 at 19:06 -0500, Brett Wynkoop wrote: > > > Greeting- > > > > > > While building a kernel the Bone stopped responding on the net and > > > this is what I found on the console: > > > > > > ti_mmchs0: Error: current cmd NULL, already done? > > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 5534, size: > > > 8192 > > [...] > > > ti_mmchs0: Error: current cmd NULL, already done? > > > ifaddr cache = 0xc1fbd700 is deleted > > > ti_mmchs0: Error: current cmd NULL, already done? > > > ti_mmchs0: Error: current cmd NULL, already done? > > snip > > > > > That's the second report recently of indefinite wait buffer. What it > > really means is that it has been waiting more than 20 seconds to pull > > a page (or block of pages) in from swap. That plus the cmd NULL > > errors tend to point in the direction of the mmchs driver. > > > > -- Ian > > Greeting- > > I am glad that I am passing on needed feedback. I did not have to > reboot the box, just waited and the console eventually responded again > and I restarted sshd. When it gets into that sort of state, can you get a response by hitting ^T on the console (or any open ssh terminal session)? If so, the line it prints may have a clue about what it's blocked on. -- Ian