From owner-freebsd-arm@FreeBSD.ORG Wed Apr 30 23:28:54 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6969D203; Wed, 30 Apr 2014 23:28:54 +0000 (UTC) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D61FA14B3; Wed, 30 Apr 2014 23:28:53 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hm4so1829127wib.17 for ; Wed, 30 Apr 2014 16:28:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/vJprbSKYDZEkovKFeA8Atcx3qRVdwoMVKqmSue0T0g=; b=vUNJVNrnFaynGz8yYghvqOM7UFMehoqN7/gBn5Dwirmecaxzc6Q6ATHmVu6HA6Bh4W VNV/XGwbVc/VJGSTJq1aB1vH1uSdkmvB88yeFaLygKTZw+l9deVou/4+bDeugaeMRsCl mVYCqgNmMp4sBSqO0ER+rBIXPnYINxg6bmfbM3sVNE7Dloq3NRAczD/XZe0LaUOkCpSt pFDVtCs8oXx5KA8wofsleerzlpb7nCwm3yeyUDcEM4N0lGS3wmQtOJDge0IfjFa3ziX7 5MU/8fQa+GvSvSBdhfDQmGhAHma2QAOeL1+529zW8ntGBqqJobaVcxs07XjUHEPx+KfQ BWbA== MIME-Version: 1.0 X-Received: by 10.194.109.6 with SMTP id ho6mr6310513wjb.21.1398900532140; Wed, 30 Apr 2014 16:28:52 -0700 (PDT) Received: by 10.217.10.195 with HTTP; Wed, 30 Apr 2014 16:28:52 -0700 (PDT) In-Reply-To: <1398897697.22079.80.camel@revolution.hippie.lan> References: <1398897697.22079.80.camel@revolution.hippie.lan> Date: Wed, 30 Apr 2014 19:28:52 -0400 Message-ID: Subject: Re: BBB @ 1Ghz hangs with 10-STABLE (11-CURRENT is ok) From: Winston Smith To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD ARM X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2014 23:28:54 -0000 On Wed, Apr 30, 2014 at 6:41 PM, Ian Lepore wrote: > That backtrace is just the idle thread; usually that's a sign that some > device driver is waiting for an interrupt to finish configuring the > device and it never gets it and just hangs. In cases like this, what should I be collecting? (assuming I can break into the debugger) > Often usb is the culprit -- > we very often rely on u-boot to set up the usb hardware and if it > doesn't the kernel hangs trying to access it. Sometimes you just need a > "usb start" in u-boot before launching the kernel or ubldr. Or maybe > there are some more fixes in 11 that haven't been merged back to 10 yet. The u-boot's are the same for both of my tests, so unless ubldr is doing this, it must be something in 11. > As to the 1ghz stuff, it was my understanding that the patches make > u-boot set the clock faster. It would probably be better to just have > our kernel code do that, but I haven't had time to look at the patches > and see how much work is involved. I looked at the patches and didn't see where it's changing the clock. However, it does appear to be changing the clock. Without the patch, I see the following: am335x_prcm0: Clocks: System 24.0 MHz, CPU 550 MHz With the patch, I see this: am335x_prcm0: Clocks: System 24.0 MHz, CPU 1000 MHz So it appears to be running at almost 2x the speed (and the caches appear to be enabled). Cool!!! -W.