From owner-freebsd-arm@FreeBSD.ORG Mon Apr 28 02:35:33 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 72DB0E0E; Mon, 28 Apr 2014 02:35:33 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (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 BE0051B76; Mon, 28 Apr 2014 02:35:32 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id w7so470935lbi.25 for ; Sun, 27 Apr 2014 19:35:29 -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:message-id:subject :from:to:cc:content-type; bh=k91JYzV8zbkQDnx1b4z4YJR+mey8W4dHBAdE8niUNps=; b=IN1my9n1J/ASeWG9KQn9pIgRv6aNJwFn1R/4Q/fyOKVthT3RyfLbvc6xGAfaMBUqi5 cmDkLRLg79Qdg+15ltvvpg1IMfpWOg4QDmVfM1I7aka9c6GIkIF9/rI2yg1VjMENBlO5 mKHyS9YFq+vnSreUHxb3EMzwapsg7xEKuFOKDU1zJUXzx6RnAvqFYqlYxyQst/6jTePg LxxxURrG3Hs8nR8pIi01SRj7AECOOsn/pk0uBdeKFC57ll4G+AePhijpPIwmQUmwgaoo bFUopw1IxLOvOlq5BCpBjqcQQklu1aobu/N6YNhd37yIQ/hETk+ui9QcQSrjMsKrgfzM wBdg== MIME-Version: 1.0 X-Received: by 10.112.139.166 with SMTP id qz6mr16139162lbb.13.1398652529697; Sun, 27 Apr 2014 19:35:29 -0700 (PDT) Sender: pkelsey@gmail.com Received: by 10.112.141.196 with HTTP; Sun, 27 Apr 2014 19:35:29 -0700 (PDT) In-Reply-To: <1398648505.61646.189.camel@revolution.hippie.lan> References: <1398618984.61646.165.camel@revolution.hippie.lan> <1398624759.61646.174.camel@revolution.hippie.lan> <1398648505.61646.189.camel@revolution.hippie.lan> Date: Sun, 27 Apr 2014 22:35:29 -0400 X-Google-Sender-Auth: Gpy8SUYjLadekh0CGD9XkJntcBc Message-ID: Subject: Re: FreeBSD-10-STABLE hangs when booting from BeagleBone Black eMMC From: Patrick Kelsey To: Ian Lepore Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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: Mon, 28 Apr 2014 02:35:33 -0000 On Sun, Apr 27, 2014 at 9:28 PM, Ian Lepore wrote: > On Sun, 2014-04-27 at 21:10 -0400, Winston Smith wrote: > > On Sun, Apr 27, 2014 at 2:52 PM, Ian Lepore wrote: > > > When it comes to the eMMC timeouts that happen after you've booted, > > > that's something in my arena, but hard for me to debug without eMMC > > > hardware. We've recently had a few changes to both the core sdhci > > > driver and to the ti_sdhci code that glues sdhci to the hardware. > > > > > > Do the timeouts happen often, or is this something you can do to > trigger > > > them? If so, it might be interesting to try to revert r264099 and see > > > if the problems go away. Those changes were related to configuring the > > > sd clock. I'm pretty sure the old code was wrong, but the replacement > > > code could have errors too. :) > > > > At this point: > > > > 1) Timeouts (11-CURRENT) > > - I have seen them twice under heavy eMMC write load, but they > > haven't seemed to cause a problem for me > > - Fabio did report the timeouts followed by a panic > > 2) I can't boot from eMMC with 10-STABLE (but I can with 11-CURRENT) > > (both using the *same* u-boot) > > > > So: > > > > A) Should I go back to 11-CURRENT? (although I need 10-something for > Golang) > > B) How can I/we help debug this further? > > > > Thanks! > > > > If you need 10 we should probably figure out what the problem is there. > If the same u-boot works on 11 and fails on 10, then the difference must > be in ubldr, and there certainly have been changes there in 11. > > The quickest way to test that theory would be to build the image for 10 > and then hand-copy the ubldr from an 11 build onto that sdcard and see > if it works. If so, we can see about merging some ubldr stuff to 10. > It may need to go into the msdos partition (I net-boot all my boards). > The issue with booting from eMMC on 10-STABLE is in ubldr. On 10-STABLE, ubldr is hardwired to boot from the first disk device, which will always be the SD card when using a u-boot that has my mmc device enumeration patches (or an equivalent). The changes that Ian and I made to ubldr would have to be MFC'd to 10-STABLE to get the behavior you want without resorting to copying ubldr built from an 11-CURRENT tree to your device. -Patrick