[PINE64] mmcsd0: aw_mmc0: Error indicated

[O. Hartmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Am Sun, 19 Aug 2018 18:53:03 +0200
Emmanuel Vadot <manu at bidouilliste.com> schrieb:

> On Sun, 19 Aug 2018 15:59:37 +0200
> "O. Hartmann" <ohartmann at walstatt.org> wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> > 
> > Am Sun, 19 Aug 2018 14:39:33 +0200
> > Emmanuel Vadot <manu at bidouilliste.com> schrieb:
> >   
> > > On Sun, 19 Aug 2018 14:15:11 +0200
> > > "O. Hartmann" <ohartmann at walstatt.org> wrote:
> > >   
> > > > -----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-----
> > > > _______________________________________________
> > > > freebsd-arm at freebsd.org mailing list
> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"    
> > > 
> > > 
> > >  Can you please provide a full bootlog (booting with boot -v)
> > > 
> > >  Also does those errors happens at boot ? after a while ? during
> > > something specific ?
> > > 
> > >  Thanks,
> > >   
> > 
> > Hello Emmanuel Vadot,
> > 
> > I have just wrapped the PINE64 away since it died again while updating the OS via
> > pkg-base.
> > 
> > The problems shown occure after a while; not while booting as far as I remember. 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".
> > 
> > I haven't observed swapping so far. I'll start a new run when I've purchased some
> > SanDisc high quality SD cards, since the ones I'm using are a bit slow.
> > 
> > It seems the problem occurs while heavy I/O is at work.
> > 
> > I'll provide the requested full bootlog later.
> > 
> > Kind regards,
> > 
> > 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.

[...]

Maybe 90% success rate:

Use a kernel with debug disabled(!) and update pkg-base remotely while running the
customised kernel. In my case, this is a 100% crash so far. I also see the problem
occuring with the vanilla GENERIC kernel, but disabling most of the dubugging options
and disabling most of the driver non-applicable to PINE64+ in a custom kernel trigger
the problem really rapidly.

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/86TrS528fyFhYlAUCW3m6FAAKCRDS528fyFhY
lORpAgChsXnCTOsPSsC6n97Hj5ae97mmyPhwcupCFS8T+vH+FJeTh2H76+mcneiH
jfeUzPyLDRG91en43TXoEeLwXSCPAf4mghqxFgulOisJlwl8PbltYJLwTcV0a2H2
jC6Wpubkz4GDwPM5vviY1VDDefUYA0fWLpNCOvtZqjJAnAdNGXae
=Y7bG
-----END PGP SIGNATURE-----