Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Aug 2018 18:53:03 +0200
From:      Emmanuel Vadot <manu@bidouilliste.com>
To:        "O. Hartmann" <ohartmann@walstatt.org>
Cc:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: [PINE64] mmcsd0: aw_mmc0: Error indicated
Message-ID:  <20180819185303.4130b0b7f78ee3df774f48e6@bidouilliste.com>
In-Reply-To: <20180819160004.37874fd0@thor.intern.walstatt.dynvpn.de>
References:  <20180819141538.1eb442ef@thor.intern.walstatt.dynvpn.de> <20180819143933.ce9bc2e3853552810db3e181@bidouilliste.com> <20180819160004.37874fd0@thor.intern.walstatt.dynvpn.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 19 Aug 2018 15:59:37 +0200
"O. Hartmann" <ohartmann@walstatt.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>=20
> Am Sun, 19 Aug 2018 14:39:33 +0200
> Emmanuel Vadot <manu@bidouilliste.com> schrieb:
>=20
> > On Sun, 19 Aug 2018 14:15:11 +0200
> > "O. Hartmann" <ohartmann@walstatt.org> wrote:
> >=20
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA512
> > >=20
> > > Running 12-CURRENT for a while now on a PINE64+, 2GB RAM from SD, I f=
ace since months
> > > those errors regarding the aw_mmc controller:
> > >=20
> > > [...]
> > >=20
> > > aw_mmc0: controller timeout
> > > aw_mmc0: timeout updating clock
> > > mmcsd0: Error indicated: 1 Timeout
> > > g_vfs_done():ufs/rootfs[WRITE(offset=3D3281551360, length=3D4096)]err=
or =3D 5
> > > aw_mmc0: controller timeout
> > > aw_mmc0: timeout updating clock
> > > mmcsd0: Error indicated: 1 Timeout
> > > g_vfs_done():ufs/rootfs[WRITE(offset=3D3282788352, length=3D4096)]err=
or =3D 5
> > > aw_mmc0: controller timeout
> > > aw_mmc0: timeout updating clock
> > > mmcsd0: Error indicated: 1 Timeout
> > > g_vfs_done():ufs/rootfs[WRITE(offset=3D3283681280, length=3D32768)]er=
ror =3D 5
> > >=20
> > > [...]
> > >=20
> > > ... and a while, the system ic completely stuck and needs hard reset.
> > >=20
> > > I can remember this error since I played around with 12-CURRENT on th=
e PINE64 and
> > > that is on various revisions since December 2017.
> > >=20
> > > Is this related to some known issues or could this be related to my h=
ardware?
> > >=20
> > > System is:
> > >=20
> > > FreeBSD 12.0-CURRENT #13 r336753: Fri Jul 27 06:02:30 CEST 2018 arm64
> > >=20
> > > I have a custom-built kernel with some add-ons like IPFW.
> > >=20
> > > Regards,
> > >=20
> > > oh
> > >=20
> > >=20
> > >=20
> > > - --=20
> > > O. Hartmann
> > >=20
> > > Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr
> > > Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs.=
 4 BDSG).
> > > -----BEGIN PGP SIGNATURE-----
> > >=20
> > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW3lfawAKCRDS528fyFhY
> > > lAppAf0SAdMz5OqhAa0bIvRxj3Ux8URIrbKPD7mZ38u2/4DQeYAE4kE9f4y39/Ei
> > > M5yXC6CGpkE9V9i4L4CpnPLb1qUiAf9IiTiyxQOOOpIwWFEY78wrrcqAN8WFgio/
> > > 53SlY/5XGktXFvSGhvMrdq2FsPzMLjvNQ+mZJ6bv5Nq4yzgJNkSq
> > > =3DGu6T
> > > -----END PGP SIGNATURE-----
> > > _______________________________________________
> > > freebsd-arm@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org=
" =20
> >=20
> >=20
> >  Can you please provide a full bootlog (booting with boot -v)
> >=20
> >  Also does those errors happens at boot ? after a while ? during
> > something specific ?
> >=20
> >  Thanks,
> >=20
>=20
> Hello Emmanuel Vadot,
>=20
> I have just wrapped the PINE64 away since it died again while updating th=
e OS via
> pkg-base.
>=20
> The problems shown occure after a while; not while booting as far as I re=
member. The
> larger the file to extract (for instance, FreeBSD-runtime pkg), the more =
probable seems
> the failure. But this is a "wild guess based on a hunch".
>=20
> I haven't observed swapping so far. I'll start a new run when I've purcha=
sed some SanDisc
> high quality SD cards, since the ones I'm using are a bit slow.
>=20
> It seems the problem occurs while heavy I/O is at work.
>=20
> I'll provide the requested full bootlog later.
>=20
> Kind regards,
>=20
> O. Hartmann

 Okay so I've already seen this issue but I never could reproduce in a
reliable way.
 If you can find a way to reproduce it with 100% success rate that
could help me.


> - --=20
> O. Hartmann
>=20
> Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr
> Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs. 4 B=
DSG).
> -----BEGIN PGP SIGNATURE-----
>=20
> iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW3l35AAKCRDS528fyFhY
> lPB5Af9p4jdGkNCkSsX2G6bQpINfYIcFrS9Mon0E/Bu9JvaK3Pegz3TaByO/h1Fw
> hVR8HzhbiuVhdJVCZfdkPsOIqdW9AgCqNxKcv6/JvLPrb/84e+UMGk5SqWcIzytc
> T+8DgOqBephnXk5WzZ131bkQYJ6aDsiHAmPbrk8rcPimQbS4q9XJ
> =3DM6VH
> -----END PGP SIGNATURE-----


--=20
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180819185303.4130b0b7f78ee3df774f48e6>