Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 May 2015 07:44:57 +0200
From:      Andreas Andersson <aandersson@tappsi.co>
To:        freebsd-arm@freebsd.org
Subject:   Re: state of FreeBSD ARM (less stable than 6 months ago)
Message-ID:  <CAOx9_ZiTuLBTWaU-a8Vm7JGkQdsOd0a1v-4q98EH%2BhA7Z6vYfw@mail.gmail.com>
In-Reply-To: <555AA2BE.4030008@foxvalley.net>
References:  <5550C252.6030001@foxvalley.net> <1431357226.2428197.265704673.6A544F74@webmail.messagingengine.com> <555177D9.8080001@foxvalley.net> <CAB=2f8zYShMH1P96MsdfP0ReMEwpkDJ%2Bq8dvMHHHjiMGmqnrqg@mail.gmail.com> <alpine.BSF.2.20.1505181523120.93723@localhost.my.domain> <555A8792.9000809@foxvalley.net> <555AA2BE.4030008@foxvalley.net>

next in thread | previous in thread | raw e-mail | index | archive | help
I can confirm this patch works. I haven't gotten any kernel panics yet.

2015-05-19 4:41 GMT+02:00 Dan Raymond <draymond@foxvalley.net>:

>
>  On Tue, 12 May 2015, Luiz Otavio O Souza wrote:
>>>
>>>  On 12 May 2015 at 00:47, Dan Raymond wrote:
>>>>
>>>>>
>>>>> 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
>>>>
>>>
>>> Luiz, the patch works for me.  Thanks!
>>>
>>> [Tested on BBB with a 2GB microSD that previously gave a WRITE timeout.]
>>>
>>> ...keith
>>>
>>
>> I was out of town for a few days but yesterday I tried the patch and I
>> was able to build my ports without a panic.  I'll continue to do some more
>> testing.
>>
>>
> Now I hit a panic while running "restart" from a terminal:
>
> panic: vm_page_unwire: page 0xc0c63e30's wire count is zero
> cpuid = 1
> KDB: enter: panic
> [ thread pid 502 tid 100081 ]
> Stopped at      $d.7:   ldrb   r15, [r15, r15, ror r15]!
> db>
> _______________________________________________
> 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"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOx9_ZiTuLBTWaU-a8Vm7JGkQdsOd0a1v-4q98EH%2BhA7Z6vYfw>