Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Apr 2014 21:10:33 -0400
From:      Winston Smith <smith.winston.101@gmail.com>
To:        Ian Lepore <ian@freebsd.org>
Cc:        FreeBSD ARM <freebsd-arm@freebsd.org>
Subject:   Re: FreeBSD-10-STABLE hangs when booting from BeagleBone Black eMMC
Message-ID:  <CADH-AwG%2BsaqXO4FYG65WMOuFyDzjbhF=a=-p3Y3En3zbcgyd6A@mail.gmail.com>
In-Reply-To: <1398624759.61646.174.camel@revolution.hippie.lan>
References:  <CADH-AwHvaVqycykONkzRsj7oD3xSi8hszvc_Wf4obC=Y_qPiaQ@mail.gmail.com> <1398618984.61646.165.camel@revolution.hippie.lan> <CADH-AwE%2B5=A4aiqbTYqor1Any1JGNhz4LHOJwfyykYU92UpirQ@mail.gmail.com> <1398624759.61646.174.camel@revolution.hippie.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 27, 2014 at 2:52 PM, Ian Lepore <ian@freebsd.org> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADH-AwG%2BsaqXO4FYG65WMOuFyDzjbhF=a=-p3Y3En3zbcgyd6A>