I’ve been testing the updated sdhost driver and just experienced a case of write errors (?) to the disk resulting in the file system switching to read only mode - possibly the same thing that happened to me during the jenkins build except this time I was logged in via ssh already so I was able to gather some debug logs.
At the time it happened I was using dd to create large files on both / and /boot to test how our update system responds to low disk space - on the /boot partition I accidentally specified a size bigger than the available free space, although that may not have been a factor. Here is the log file:
This is on my same samsung 32GB card which requires the cmd23quirk workaround to avoid hangs. (Eg the latest kernels that have removed cmd23 quirk by default cause random disk IO freezes on this card - I either have to use sdhost or bcm2835_mmc.mmc_debug=0x2000 in cmdline.txt to re-enable cmd23 quirk be able to use this card)
Sorry to say I also need to report an issue. I am the person with the Lexar card earlier in the thread. Same card, new driver. Ran for approx. a day, fairly light usage. Keep in mind, this card wouldn’t last more then a few minutes with the old driver.
2 days ago, I went to watch the trailer of a movie and around 2 mins. into the trailer, the Pi 2 hung up. Hard. I couldn’t ssh into the Pi. I needed to do a power cycle.
Needless to say, no log…
I then edited config.txt and removed the sdhost section. It’s been running a few days now (and played the trailer) fine.
DBMandrake, you mention a cmd23 fix. Can you point me to more info? The hang up I experienced sounds suspiciously close…
ALLOW_CMD23 is set to 0 in the sdhost driver, and it’s not exported as a parameter, so changing it won’t be trivial for you (you’d need to recompile the driver).
The first 5 were on the root file system and didn’t experience problems, the last two were on the boot partition, the first of which - 300MB was a typo that caused the partition to run right out of space as there was only 58MB free. This seemed to be when the errors occurred but it could have just been a coincidence.
This driver is not part of the standard kernel in the release version of OSMC at the moment.
The next kernel update should include the driver but it will most likely be disabled by default, but possible to enable just by editing config.txt for those that want to experiment with it.
Simple question… i have “installed” this driver about three month ago… after a lot of upgrade of main distro of osmc i need to re-apply this mod every time ?