Briefly: I now think this is “user error” - mine - of some sort, and I don’t want to bother the forums with the issue until I have more confidence that there is actually an issue. I’m going to try to get this post closed or demoted or, ideally, deleted.
I do appreciate the links to more information.
Since you asked, and if you are still reading:
Yesterday, the problem occurred yesterday on both Paperspace P6000 GPU (CUDA 9.2, I think), and C2 (non-GPU) VMs.
Two weeks ago, I did not see this behavior in either environment. And I don’t see it on my local machine (non-Nvidia GPU, so I run Torch in CPU mode only)
Today I updated fastai and associated packages, and re-tried. It now seems to work on P4000 GPU machines (tho I’m now seeing other strange import issues), but not on the C2 machines. Hence my reluctance to pursue this until I understand a little more about what is going wrong.
Hi @mcsieber did you ever get to the bottom of this? I’ve just hit the same error… Im using cloud server with CPU just to get the data set labelled and first loop running on a cheap machine before switching over to GPU. Could this be why?