Comment 8 for bug 1793901

My system has changed somewhat, as I moved my root / to bcache with a kernel that worked.
Still, I installed the mainline build, and the oops did not occur so far. However I also cannot run that kernel properly as it does not seem to work well with Nvidia graphics. (very low resolution and probably wrong driver)
However I am not sure that ensures that the problem is fixed, as when I rebooted with the kernel where the problem did occur, it also did not occur anymore (or at least it didn't say) but as stated above, the setup is not the same as the bcache device is now /. I made a separate, similar bcache device (in the same devices, with the same settings), but there the problem also didn't occur so far. The only thing I couldn't didn't replicate (apart from the partitions being at different places) was that when the error occured, at first the caching device didn't seem to be properly registered, but when adding it manually it said it was. Finally after running partprobe and/or rebooting this was remedied. When now recreating a fresh bcache device, there were no issues with registering/recognizing, and I am not sure how to replicate this.