From owner-freebsd-arm@FreeBSD.ORG Tue Oct 30 16:03:11 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 91F8E89B for ; Tue, 30 Oct 2012 16:03:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 56AB38FC18 for ; Tue, 30 Oct 2012 16:03:11 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so194677dad.13 for ; Tue, 30 Oct 2012 09:03:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=166rA2vyDZDRp8jJCM7POYbj0J5ILSFszTZgw5tTH6g=; b=bpFTe4hYHKs9e+1lzXOJX0jTyIBmz+qgbHBZ7i2HYYYcHaBucDJuJojHqW2F/txjYh pFC+KnStvUr5m04KcyGenxHIUFqcU0R41BfxqdDwgpLyA1/jnyD81R7Sca0HPTwRJkn9 zJtZ5WKa7KZ32He7sopfpWXfRuD/ac9L9n7JYvJtwWfsAYsquHdsT5awKUza7KLKLL6s QbxV/BlYqsNriu58CqIH0XX5mke/5ANqOYgEGQD3RDBMpDFeWvz3WUXHPV6nahCY6PJ9 c2qfgWzHHxCnU/bXY6qrGi295YuOlsOzEtmvPCqbT0c9Cuq3Ah9mYi1E+AkoN994KXfv ASqw== MIME-Version: 1.0 Received: by 10.68.223.37 with SMTP id qr5mr104064865pbc.101.1351612990762; Tue, 30 Oct 2012 09:03:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.146.233 with HTTP; Tue, 30 Oct 2012 09:03:10 -0700 (PDT) In-Reply-To: References: <2E208EEB-B2CF-4AC6-B420-03FB4CF08041@freebsd.org> <1351522908.1123.356.camel@revolution.hippie.lan> <1351550400.1123.364.camel@revolution.hippie.lan> Date: Tue, 30 Oct 2012 09:03:10 -0700 X-Google-Sender-Auth: RyxclkbLDEQg-VWjuX5xZAW3HNM Message-ID: Subject: Re: BeagleBone questions (was Re: Towards an ARM system-building script) From: Adrian Chadd To: Alie Tan Content-Type: text/plain; charset=ISO-8859-1 Cc: "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, 30 Oct 2012 16:03:11 -0000 On 30 October 2012 03:42, Alie Tan wrote: >> More directly on the OP's point, I wonder if the combo of the system not >> fully booting and too much heat imply that something has gone into a >> tight loop somewhere. > Is there any way to debug/detect this issue? > I cant see any heavy processes from 'top' Well, the real way would be to get PMC up and then see how many cycles are spent in the halt state, versus in the "spin" state inside the idle loop. I just looked at the idle loop and it calls cpu_sleep(0); - the implementations of that _seem_ to enter a CPU wait state, rather than just spinning and chewing all the CPU cycles available. Which CPU type is the RPI? Is it using the armv7 machdep code? Adrian