From owner-freebsd-arm@FreeBSD.ORG Mon Apr 28 01:28:29 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E41EB445 for ; Mon, 28 Apr 2014 01:28:29 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B6E771619 for ; Mon, 28 Apr 2014 01:28:29 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WeaMu-0006Os-Bu; Mon, 28 Apr 2014 01:28:28 +0000 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 s3S1SQPY014329; Sun, 27 Apr 2014 19:28:26 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19m6SdmC3JGH57fxBAlfPrk Subject: Re: FreeBSD-10-STABLE hangs when booting from BeagleBone Black eMMC From: Ian Lepore To: Winston Smith In-Reply-To: References: <1398618984.61646.165.camel@revolution.hippie.lan> <1398624759.61646.174.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Sun, 27 Apr 2014 19:28:25 -0600 Message-ID: <1398648505.61646.189.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit 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 01:28:30 -0000 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). -- Ian