sjorge: What cpu are you advertising?

While I know it's some kind of Intel, the specific one's important.

you know when you see a bug that makes your brain itch?

→ BUG 16662: illumos should not be dishonest about radixes (New)

alanc: since you enjoy these, or seem to

richlowe: those make me channel chief inspector dreyfus.. especially when i see a message with a value like '12' but is actually hex w/o the 0x

rmustacc Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz CPU

sjorge - 0x140 on Intel is MSR_MISC_FEATURE_ENABLES, so it seems like the guest is trying to disable all of the "misc features". bhyve doesn't support/emulate that MSR so it ends in that trace. I'd start by trying to find where it does it in the Linux source, and when/why it was introduced, then we can decide if we should tweak bhyve to do something here (like accept writing a 0 as a NOP).

It might also be best to leave it as-is so the guest knows it is not supported, but I am not a fan of boot messages containing backtraces when running under bhyve if we can do something better.

there's also lists.freebsd.org/archives/dev-comm…c-branches/2023-January/009071.html

uh, lore.kernel.org/kvm/20190329135422.…5046-3-xiaoyao.li⊙lic/T

sorry

it seems the cpuid faulting stuff is it?

obvious searching doesn't find any other writes

and github.com/torvalds/linux/blob/0c38…bd/arch/x86/kernel/cpu/intel.c#L587

but that's hardly recent

torvalds/linux 90218ac apparently

Is there a doc for the correct process when replacing NVMe drives? Just managed to wedge a SmartOS server swapping disks. Simply pulled the old disk and inserted the new. Then 'nvmeadm list' hung. After a forced reboot things look okay and new disk is showing in the list output.

Meths : I can only remember youtube.com/watch?v=UICLVrtHOUc&lis…owDoi6pWLkwdSpCQs2obgRX4VZ&index=16 regarding NVMEs

Meths: Would have expected it to work, assuming a hotplugable slot. If you get that kind of hang again, a crash dump would help.

If we didn't get notified about the removal, there will be limitations to what we can do.

Thanks neuroserve, interesting video. May try using the cfgadm commands next time.

rmustacc: Will do on the dump if we duplicate it. The logs seemed to show things being notified and picking up on the activity. We seemed to get notice of the pci-level and disk device level removal. On insertion it only logged activity at the pci layer.

Hmm, what bits were you using?

As there was a bunch to make sure the device was auto-onlined, but either way that shouldn't have led to an nvmeadm list hang.

The drives are Samsung 8TB, AMD EPYCs and it was running 20220310, now following the reboot we're on 20240627.

SmartOS that is.

Let me double check but I think a bunch of the fixes and auto-online stuff postdates that smartos release.

Yeah, illumos#15942 for example.

And likely illumos#15689.

andyf I'm still on Ubuntu LTS 22.04 (as you can't upgrade to 24.04 yet) so I was really surprised to see it, it does seem 'harmless' but yeah the trace is just nasty

Nice digging from richlowe, is that something we already pulled in?

I thank from the trace its the one in intel.c ?

*think