mmcsd0 timeouts on Beaglebone Black after recent -CURRENT update

[Paul Mather]

I upgraded my FreeBSD/arm 11-CURRENT Beaglebone Black recently and, ever since, it has had mmcsd0 storage problems that cause the system to become effectively unusable.

Since the update (to r289141), I get messages like this on the console:

mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[READ(offset=1005948928, length=4096)]error = 5
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[READ(offset=1005953024, length=4096)]error = 5
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[READ(offset=1005957120, length=4096)]error = 5
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[READ(offset=1005961216, length=4096)]error = 5
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[READ(offset=1005969408, length=4096)]error = 5
g_vfs_done():mmcsd0s2a[READ(offset=1522622464, length=4096)]error = 5
g_vfs_done():mmcsd0s2a[READ(offset=1504862208, length=4096)]error = 5
g_vfs_done():mmcsd0s2a[READ(offset=2521161728, length=4096)]error = 5
g_vfs_done():mmcsd0s2a[READ(offset=2502615040, length=4096)]error = 5
[[...]]
g_vfs_done():mmcsd0s2a[READ(offset=756510720, length=4096)]error = 5
g_vfs_done():mmcsd0s2a[READ(offset=756514816, length=4096)]error = 5
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[READ(offset=685047808, length=32768)]error = 5
swap_pager: I/O error - pagein failed; blkno 964,size 32768, error 5
vm_fault: pager read error, pid 429 (syslogd)
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[READ(offset=131072, length=16384)]error = 5
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[WRITE(offset=273498112, length=16384)]error = 5
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[WRITE(offset=273498112, length=16384)]error = 5
mmcsd0: Error indicated: 1 Timeout
g_vfs_done():mmcsd0s2a[WRITE(offset=269680640, length=28672)]error = 5
g_vfs_done():mmcsd0s2a[WRITE(offset=249593856, length=16384)]error = 5



I upgraded via a cross-build on FreeBSD/amd64 10-STABLE.

Right now, the system is responding to pings, but anything that requires file system access is wedged, meaning the system is pretty much unusable right now.

It had been VERY stable prior to the upgrade.

Is anyone else encountering a similar problem?

Cheers,

Paul.