From owner-freebsd-arm@FreeBSD.ORG Mon May 18 19:26:51 2015 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 40669C8 for ; Mon, 18 May 2015 19:26:51 +0000 (UTC) Received: from courriel.site.uottawa.ca (eecsmail.engineering.uottawa.ca [137.122.24.224]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.site.uottawa.ca", Issuer "PositiveSSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F209D187E for ; Mon, 18 May 2015 19:26:50 +0000 (UTC) Received: from [10.0.2.15] (ppp-66-225-169-32.vianet.ca [66.225.169.32]) (authenticated bits=0) by courriel.site.uottawa.ca (8.14.5/8.14.5) with ESMTP id t4IJQfST079211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 May 2015 15:26:42 -0400 (EDT) (envelope-from kwhite@site.uottawa.ca) Date: Mon, 18 May 2015 15:26:38 -0400 (EDT) From: Keith White X-X-Sender: kwhite@localhost.my.domain To: Luiz Otavio O Souza cc: Dan Raymond , "freebsd-arm@freebsd.org" Subject: Re: state of FreeBSD ARM (less stable than 6 months ago) In-Reply-To: Message-ID: References: <5550C252.6030001@foxvalley.net> <1431357226.2428197.265704673.6A544F74@webmail.messagingengine.com> <555177D9.8080001@foxvalley.net> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2015 19:26:51 -0000 On Tue, 12 May 2015, Luiz Otavio O Souza wrote: > On 12 May 2015 at 00:47, Dan Raymond wrote: >> On 5/11/2015 9:13 AM, Mark Felder wrote: >>> >>> On Mon, May 11, 2015, at 09:53, Dan Raymond wrote: >>>> >>>> I've been running an email and web server using FreeBSD 11 on a >>>> Raspberry Pi B+ since November. It has crashed 3 times since then >>>> (roughly every two months). I'm currently running r277334. I thought >>>> I'd try the latest build to see if stability has improved. I purchased a >>>> Raspberry Pi 2 and used the latest crochet to built r282738. No >>>> problems building it and it booted up fine. However, it crashes about >>>> an hour into building some ports I use for my server (nginx, php, >>>> etc.). I tried twice last night and it crashed both times. Is anybody >>>> looking into these stability issues? >>>> >>> RPi2 support is something like less than a week old for SMP and DMA >>> transport. I'm not sure more than a handful of people have actually >>> tried it yet. The bugs here will be worked out in time, but if you have >>> any core dumps or info that can assist in tracking down issues you're >>> experiencing that would certainly be appreciated. >>> >> >> These panics always seem to be mmcsd related. I doubt it has anything to do >> with RPi2 or SMP. >> >> sdhci_bcm0-slot0: Controller timeout >> sdhci_bcm0-slot0: ============== REGISTER DUMP ============== >> sdhci_bcm0-slot0: Sys addr: 0x4d295a00 | Version: 0x00009902 >> sdhci_bcm0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000020 >> sdhci_bcm0-slot0: Argument: 0x002d19c0 | Trn mode: 0x0000193a >> sdhci_bcm0-slot0: Present: 0x01ff0506 | Host ctl: 0x00000003 >> sdhci_bcm0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 >> sdhci_bcm0-slot0: Wake-up: 0x00000000 | Clock: 0x00000507 >> sdhci_bcm0-slot0: Timeout: 0x0000000e | Int stat: 0x00000010 >> sdhci_b >> >> >> >> mmcsd0: Error indicated: 1 Timeout >> g_vfs_done():mmcsd0s2a[WRITE(offset=1460830208, length=24576)]error = 5 >> panic: No b_bufobj 0xd767ca00 >> cpuid = 1 >> KDB: enter: panic >> [ thread pid 12 tid 100013 ] >> Stopped at $d.7: ldrb r15, [r15, r15, ror r15]! >> db> > > Hm, I have seen this already, it is the sdhci software timeout. > > The 'happens at night' part rings a bell for me. > > In my case it happened only with a card that has failed a few weeks > later, so I thought it was a pre-fail case. > > But in certain cases (depending on the card) I think this timeout can > be triggered with normal usage. > > Please try the attached patch and let me know if it works for you. > > Luiz > > Index: sys/dev/sdhci/sdhci.c > =================================================================== > --- sys/dev/sdhci/sdhci.c (revision 282210) > +++ sys/dev/sdhci/sdhci.c (working copy) > @@ -872,7 +872,7 @@ > /* Start command. */ > WR2(slot, SDHCI_COMMAND_FLAGS, (cmd->opcode << 8) | (flags & 0xff)); > /* Start timeout callout. */ > - callout_reset(&slot->timeout_callout, 2*hz, sdhci_timeout, slot); > + callout_reset(&slot->timeout_callout, 10*hz, sdhci_timeout, slot); > } > > static void > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" Luiz, the patch works for me. Thanks! [Tested on BBB with a 2GB microSD that previously gave a WRITE timeout.] ...keith