Beaglebone Black: crash during portsnap extract

Jason Birch jbirch at jbirch.net
Fri Feb 21 14:57:18 UTC 2014


I think `portsnap fetch` is sufficient to trigger this with the snapshots
from Feb 16th.

    $ uname -a
    FreeBSD beaglebone 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r261948: Sun
Feb 16 18:05:23 UTC 2014
root at grind.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/BEAGLEBONE
 arm

    [ via ssh ]
    # portsnap fetch
    Looking up portsnap.FreeBSD.org mirrors... none found.
    Fetching snapshot tag from portsnap.FreeBSD.org... done.
    Fetching snapshot metadata... done.
    Fetching snapshot generated at Fri Feb 21 00:01:19 UTC 2014:
    226ed4090b222d40e48a3ad2f610dd81bef3c38f53deeb100% of   69 MB  659 kBps
01m47s
    Extracting snapshot...
    [ Halts here ]

    [ Over in the UART world ]
    mmcsd0: Error indicated: 1 Timeout
    mmcsd0: Error indicated: 4 Failed
    mmcsd0: Error indicated: 4 Failed
    ... [ 30 identical lines omitted] ...
    mmcsd0: Error indicated: 4 Failed
    mmcsd0: Error indicated: 4 Failed
    mmcsd0: Error indicag_vfs_done():mmcsd0s2a[WRITE(offset=998113280,
length=16384)]error = 5
    panic: No b_bufobj 0xc11d0c20
    KDB: enter: panic
    [ thread pid 12 tid 100007 ]
    Stopped at      $d:     ldrb    r15, [r15, r15, ror r15]!
    db> c
    Uptime: 6m57s
    Automatic reboot in 15 seconds - press a key on the console to abort

I see the same behaviour performing `portsnap fetch` over the UART
connection. There's some trace/proc/reg love at
https://gist.github.com/jbirch/9135611, but I'm afraid I don't know much
more here. This is reliably reproducible so I'll be using it to learn how
to effectively use ddb.

JB


On Mon, Feb 10, 2014 at 6:18 AM, <hhh at sdf.org> wrote:

> Hi all,
>
> my system is crashing every time I try to extract snapshot of ports tree
> (portsnap extract).  I had no problems coping the ports tree from a
> different machine using sftp.  Do you have suggestions why is it
> happening?
>
>
> The system (uname -a):
>
> FreeBSD beaglebone 10.0-STABLE FreeBSD 10.0-STABLE #0 r261548: Thu Feb  6
> 14:41:33 UTC 2014     root at localhsot:/root/crochet-freebsd/work/obj/arm.armv6/usr/src/sys/BEAGLEBONE
>  arm
>
>
> And the message:
>
> sdhci_ti0-slot0: Got data interrupt 0x00000010, but there is no active
> command.
> sdhci_ti0-slot0: ============== REGISTER DUMP ==============
> sdhci_ti0-slot0: Sys addr: 0x00000000 | Version:  0x00003101
> sdhci_ti0-slot0: Blk size: 0x00000200 | Blk cnt:  0x00000001
> sdhci_ti0-slot0: Argument: 0x00005d16 | Trn mode: 0x0000183a
> sdhci_ti0-slot0: Present:  0x01f70000 | Host ctl: 0x00000006
> sdhci_ti0-slot0: Power:    0x0000000d | Blk gap:  0x00000000
> sdhci_ti0-slot0: Wake-up:  0x00000000 | Clock:    0x00000007
> sdhci_ti0-slot0: Timeout:  0x0000000d | Int stat: 0x00000000
> sdhci_ti0-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb
> sdhci_ti0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000
> sdhci_ti0-slot0: Caps:     0x06e10080 | Max curr: 0x00000000
> sdhci_ti0-slot0: ===========================================
> mmcsd0: Error indicated: 2 Bad CRC
> sdhci_ti0-slot0: Got data interrupt 0x00000010, but there is no active
> command.
> sdhci_ti0-slot0: ============== REGISTER DUMP ==============
> sdhci_ti0-slot0: Sys addr: 0x00000000 | Version:  0x00003101
> sdhci_ti0-slot0: Blk size: 0x00000200 | Blk cnt:  0x00000008
> sdhci_ti0-slot0: Argument: 0x001e42be | Trn mode: 0x0000193a
> sdhci_ti0-slot0: Present:  0x01f70000 | Host ctl: 0x00000006
> sdhci_ti0-slot0: Power:    0x0000000d | Blk gap:  0x00000000
> sdhci_ti0-slot0: Wake-up:  0x00000000 | Clock:    0x00000007
> sdhci_ti0-slot0: Timeout:  0x0000000d | Int stat: 0x00000000
> sdhci_ti0-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb
> sdhci_ti0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000
> sdhci_ti0-slot0: Caps:     0x06e10080 | Max curr: 0x00000000
> sdhci_ti0-slot0: ===========================================
> mmcsd0: Error indicated: 1 Timeout
> sdhci_ti0-slot0: Got data interrupt 0x00000010, but there is no active
> command.
> sdhci_ti0-slot0: ============== REGISTER DUMP ==============
> sdhci_ti0-slot0: Sys addr: 0x00000000 | Version:  0x00003101
> sdhci_ti0-slot0: Blk size: 0x00000200 | Blk cnt:  0x00000008
> sdhci_ti0-slot0: Argument: 0x001e42fe | Trn mode: 0x0000193a
> sdhci_ti0-slot0: Present:  0x01f70000 | Host ctl: 0x00000006
> sdhci_ti0-slot0: Power:    0x0000000d | Blk gap:  0x00000000
> sdhci_ti0-slot0: Wake-up:  0x00000000 | Clock:    0x00000007
> sdhci_ti0-slot0: Timeout:  0x0000000d | Int stat: 0x00000000
> sdhci_ti0-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb
> sdhci_ti0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000
> sdhci_ti0-slot0: Caps:     0x06e10080 | Max curr: 0x00000000
> sdhci_ti0-slot0: ===========================================
> mmcsd0: Error indicated: 1 Timeout
> g_vfs_done():mmcsd0s2a[WRITE(offset=10072064, length=512)]error = 5
> panic: brelse: inappropriate B_PAGING or B_CLUSTER bp 0xcd17df48
> KDB: enter: panic
> [ thread pid 12 tid 100007 ]
> Stopped at      $d:     ldrb    r15, [r15, r15, ror r15]!
> db>
>
>
> Thank you for help
> Henryk
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>


More information about the freebsd-arm mailing list