-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Just after boot a focal image panics propolis #333
Comments
Core file available here: catacomb:/data/staff/core/gimlet-sn21/propolis-issue-333 |
Here is the propolis server log |
Crucible version (from omicron package-manifest) is:
|
I was able to reproduce this on a second attempt. I suspect a version mismatch between the propolis version of Crucible and Omicrons version may be having an impact here. There are some differences in the message passing protocol between these two versions. |
Confirmed this was the issue. I've filed an issue on the Crucible repo to better track and report over the wire version mismatch, and we probably need to move omicron to match the propolis version (or make them all use the latest crucible). |
sigh I also confirmed that Omicron is using a version of propolis that is using a version of crucible that matches with what Omicron is using, so there was no mismatch for stock Omicron bits. |
I'm also seeing a similar panic with different values:
this is booting a omicron: cb3d713a I haven't seen a focal image panic yet on my setup |
I have three dead propolis zones, and the panic seems to correlate with reading and writing the same MSR:
|
Just throwing this in here since I looked it up earlier. The MSR in @jmpesp's rdmsr/wrmsr output corresponds to MSR The value it's writing is 0x4000_0000_0000, which is setting bit 46. Per the AMD Bios and Kernel Developer's Guide, that is:
|
Running latest Omicron (on sn21) I encountered a panic in propolis-server after a first boot of a newly created Ubuntu Focal instance.
The tail of the propolis-server log looks like this:
The stack of the thread that panic'd is:
The text was updated successfully, but these errors were encountered: