From owner-freebsd-arm@FreeBSD.ORG Tue Feb 12 06:59:29 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 578BC985; Tue, 12 Feb 2013 06:59:29 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 15D39810; Tue, 12 Feb 2013 06:59:28 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r1C6xS9D019091; Tue, 12 Feb 2013 06:59:28 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 4iyym6qi3q9e4gxb93cwixeyke; Tue, 12 Feb 2013 06:59:27 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: BeagleBone locked up Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <4AF15BB9-4174-4564-A770-BF9EB9D447F5@kientzle.com> Date: Mon, 11 Feb 2013 22:59:26 -0800 Content-Transfer-Encoding: 7bit Message-Id: <71E78969-89F2-42B1-9E3C-6F0A8D83D9FC@kientzle.com> References: <20130210231709.26f122dc@ivory.local> <20130211190606.1c985baf@ivory.local> <1360629932.4545.150.camel@revolution.hippie.lan> <4AF15BB9-4174-4564-A770-BF9EB9D447F5@kientzle.com> To: Tim Kientzle X-Mailer: Apple Mail (2.1283) Cc: freebsd-arm@freebsd.org, Brett Wynkoop , Ian Lepore 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 06:59:29 -0000 On Feb 11, 2013, at 10:38 PM, Tim Kientzle wrote: > > On Feb 11, 2013, at 4:45 PM, 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? >>> >>> The interesting thing is I have seen this same swap_pager error message >>> on my 32 bit x86 FreeBSD 9 box when it drops it's IDE disks and goes >>> off the net as well. >>> >>> The last I saw of the kernel recompile it was at linking just before it >>> locked up. >>> >>> Ideas? >> >> 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. > > This is something that's degraded fairly recently. > I only started seeing these in the last week or so. > > And the BeagleBone MMCHS driver has not been > touched in a very long time. Although it seems that there has recently been a big bump in memory requirements for compiling, so maybe this is just a side-effect of hammering the swap harder than before. Tim