Date: Sun, 19 Aug 2018 14:15:11 +0200 From: "O. Hartmann" <ohartmann@walstatt.org> To: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: [PINE64] mmcsd0: aw_mmc0: Error indicated Message-ID: <20180819141538.1eb442ef@thor.intern.walstatt.dynvpn.de>
index | next in thread | raw e-mail
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Running 12-CURRENT for a while now on a PINE64+, 2GB RAM from SD, I face since months those errors regarding the aw_mmc controller: [...] aw_mmc0: controller timeout aw_mmc0: timeout updating clock mmcsd0: Error indicated: 1 Timeout g_vfs_done():ufs/rootfs[WRITE(offset=3281551360, length=4096)]error = 5 aw_mmc0: controller timeout aw_mmc0: timeout updating clock mmcsd0: Error indicated: 1 Timeout g_vfs_done():ufs/rootfs[WRITE(offset=3282788352, length=4096)]error = 5 aw_mmc0: controller timeout aw_mmc0: timeout updating clock mmcsd0: Error indicated: 1 Timeout g_vfs_done():ufs/rootfs[WRITE(offset=3283681280, length=32768)]error = 5 [...] ... and a while, the system ic completely stuck and needs hard reset. I can remember this error since I played around with 12-CURRENT on the PINE64 and that is on various revisions since December 2017. Is this related to some known issues or could this be related to my hardware? System is: FreeBSD 12.0-CURRENT #13 r336753: Fri Jul 27 06:02:30 CEST 2018 arm64 I have a custom-built kernel with some add-ons like IPFW. Regards, oh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW3lfawAKCRDS528fyFhY lAppAf0SAdMz5OqhAa0bIvRxj3Ux8URIrbKPD7mZ38u2/4DQeYAE4kE9f4y39/Ei M5yXC6CGpkE9V9i4L4CpnPLb1qUiAf9IiTiyxQOOOpIwWFEY78wrrcqAN8WFgio/ 53SlY/5XGktXFvSGhvMrdq2FsPzMLjvNQ+mZJ6bv5Nq4yzgJNkSq =Gu6T -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180819141538.1eb442ef>