From owner-freebsd-arm@FreeBSD.ORG Mon Apr 28 01:10:35 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 8D3092DF; Mon, 28 Apr 2014 01:10:35 +0000 (UTC) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (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 0294614B0; Mon, 28 Apr 2014 01:10:34 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id q5so4925706wiv.10 for ; Sun, 27 Apr 2014 18:10:33 -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=3kIUJNe1tdkRnnqAPhiLw0U6Xn2Gg8ogg5nWRpBxZL4=; b=KpKOLVG2RnVorZL6GNcn7CWk01xlmtmXXDtyiWRYuJ89J7gFlHVoDwy+yeoMpBU/Ar vLYDQYTZbQtJVQMW2qsrq3Z8HvOrb2mCj8WTnS51FEaD53K4qkXvqsR6zETqxT2uZOJF 43S/DqDs3IpWvz5jrjdsYNJJtAa7ih3z7H+86b5N7y+XKQ90oUJKcMDsiYb6m+6QYXC2 Xul9BcWPtZeWKpp06MctPZFeZxeTUPjCARnr+k1NP6Ay25BMkJwwlYJYL1H4WSZGT9Xx mCw0h2MsWgy8qY2OpRCOvS8K+3RzEpMHavY9DjE0YIESh/c61ZWFcp4qE+o2VJrYrJv+ /uTg== MIME-Version: 1.0 X-Received: by 10.194.71.164 with SMTP id w4mr16687105wju.0.1398647433290; Sun, 27 Apr 2014 18:10:33 -0700 (PDT) Received: by 10.217.10.195 with HTTP; Sun, 27 Apr 2014 18:10:33 -0700 (PDT) In-Reply-To: <1398624759.61646.174.camel@revolution.hippie.lan> References: <1398618984.61646.165.camel@revolution.hippie.lan> <1398624759.61646.174.camel@revolution.hippie.lan> Date: Sun, 27 Apr 2014 21:10:33 -0400 Message-ID: Subject: Re: FreeBSD-10-STABLE hangs when booting from BeagleBone Black eMMC 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: Mon, 28 Apr 2014 01:10:35 -0000 On Sun, Apr 27, 2014 at 2:52 PM, Ian Lepore wrote: > Just ignore the LORs, or even better, turn off WITNESS. IMO, it has > become useless, because nobody fixes them anymore, or even responds to > reports of them other than to sometimes post a link to a site that > tracks "known LORs", but that site hasn't been updated for like 6 years. That's kind of what I figured; I will turn off WITNESS. > 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! -W