3 ms·
TL;DR: Run-time dispatch in OpenBLAS chose code matching the CPU reported by the VM, thereby employing instructions that the real CPU doesn't have -> SIGILL. I
by MauranKilom 4y ago
TL;DR: Run-time dispatch in OpenBLAS chose code matching the CPU reported by the VM, thereby employing instructions that the real CPU doesn't have -> SIGILL.
I don't understand the "one day later my file system was broken" thing at the end though. Was this supposed to have any relation to the crash at all? It's way more mysterious than "SIGILL due to wrongly reported CPU type", but no elaboration is provided. What did the author even try to communicate there?
- habibur 4y ago> ... thing at the end though guess that was like adding a random personal fact at the end. No relation with the article.
- nieve 4y agoThey said they couldn't run certain things again, I assume they were explaining why they couldn't.
- deleted 4y ago[deleted]
- MBCook 4y agoSince the author was dealing with a VM, my only guess is that for some reason the VM started receiving a different fake CPU? Maybe something like the virtualization software had changed? And that apparently caused file system mounting problems??? I agree it wasn’t clear at all.
- GrayShade 4y agoAuthor here. I don't know if the provider just changed the CPU type or if someone else ran into the same problem on that VM and complained to them. The file system error is probably unrelated, I've seen a couple of those on other VMs from the same provider, but this time it probably caused it to fail to boot properly. More mysterious, but mostly out of my hands.
- mvuksano 4y agoOut of curiosity, who is the provider?