From owner-freebsd-arm@freebsd.org Tue Oct 13 15:23:38 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56F44A116EE for ; Tue, 13 Oct 2015 15:23:38 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 34DAD144C for ; Tue, 13 Oct 2015 15:23:37 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 962515A8 for ; Tue, 13 Oct 2015 11:17:18 -0400 (EDT) From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: mmcsd0 timeouts on Beaglebone Black after recent -CURRENT update Message-Id: Date: Tue, 13 Oct 2015 11:17:19 -0400 To: freebsd-arm Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) 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: Tue, 13 Oct 2015 15:23:38 -0000 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=3D1005948928, length=3D4096)]error =3D = 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[READ(offset=3D1005953024, length=3D4096)]error =3D = 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[READ(offset=3D1005957120, length=3D4096)]error =3D = 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[READ(offset=3D1005961216, length=3D4096)]error =3D = 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[READ(offset=3D1005969408, length=3D4096)]error =3D = 5 g_vfs_done():mmcsd0s2a[READ(offset=3D1522622464, length=3D4096)]error =3D = 5 g_vfs_done():mmcsd0s2a[READ(offset=3D1504862208, length=3D4096)]error =3D = 5 g_vfs_done():mmcsd0s2a[READ(offset=3D2521161728, length=3D4096)]error =3D = 5 g_vfs_done():mmcsd0s2a[READ(offset=3D2502615040, length=3D4096)]error =3D = 5 [[...]] g_vfs_done():mmcsd0s2a[READ(offset=3D756510720, length=3D4096)]error =3D = 5 g_vfs_done():mmcsd0s2a[READ(offset=3D756514816, length=3D4096)]error =3D = 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[READ(offset=3D685047808, length=3D32768)]error =3D = 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=3D131072, length=3D16384)]error =3D 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[WRITE(offset=3D273498112, length=3D16384)]error =3D= 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[WRITE(offset=3D273498112, length=3D16384)]error =3D= 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[WRITE(offset=3D269680640, length=3D28672)]error =3D= 5 g_vfs_done():mmcsd0s2a[WRITE(offset=3D249593856, length=3D16384)]error =3D= 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.=20=