14:17:21 <KungFuJesus> hmm, ran into this guy again on one of our machines over the weekend: https://www.illumos.org/issues/15024
14:17:22 <fenix> → BUG 15024: NFS can exhaust pool threads getting RPCSEC_GSS credentials (In Progress) | https://code.illumos.org/c/illumos-gate/+/2402
14:18:06 <KungFuJesus> We insisted our users not use krb5 for now, but it does seem to be an issue.  Usually we'd see it after a DC reboot but there's was nothing to indicate what provoked it this time
16:22:20 <nahamu> Does anyone have notes on how to perform the workaround for zenbleed on illumos?
16:27:16 <papertigers> sounds like it's an eventual microcode update
16:27:20 <papertigers> that looks nasty
16:27:30 <andyf> You could pull the microcode from linux-firmware and apply it
16:29:07 <andyf> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amd
16:30:17 <rmustacc> Yes, I'd recommend just hot-loading the microcode. We'll get stuff written up and sent out before long.
16:33:14 <nahamu> I'll keep an eye out.
16:33:15 <andyf> Quick instruction: download the fam17h file, put it on your system and rename it to anything starting with `amd`, then `ucodeadm -u <file>` to load it. `ucodeadm -v` will show the version on each CPU.
16:33:31 <nahamu> Thanks andyf!
16:35:29 <papertigers> andyf: what's the difference between model0xh.sbin and model3xh.sbin
16:35:53 <andyf> The correct file is https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin (and there's a detached signature in the same .asc if you want to verify it against AMD's published keys)
16:35:59 <andyf> papertigers - my first link was wrong, sorry.
16:37:24 <papertigers> thanks
16:37:53 <jbk> OA
16:38:36 <nahamu> If I tried to load in the wrong file, would the system protect itself, or is this a pretty dangerous operation?
16:38:43 <jbk> well at least the ^[[ didn't come through :)
16:41:39 <papertigers> rmustacc / andyf: do you know if I need to apply that on zen3? Seems like my 5600X is post zen2
16:41:44 <rmustacc> papertigers: You do not.
16:41:51 <rmustacc> This is noted as only impacting Zen 2.
16:41:58 <papertigers> thanks -- I will just apply it to my Rome box then
16:42:23 <rmustacc> We'll get more info sent out and with our standard security impact, action required, etc. in a little bit.
16:43:24 <andyf> nahamu - it should not accept an incorrect update. Note that this is not persistent though, it will need doing after every reboot if you load it manually.
16:43:35 <nahamu> andyf: cool. Thanks.
16:43:38 <papertigers> thanks ucodeadm reports I went from 0x8301072 -> 0x830107a if you are curious nahamu 
16:44:13 <nahamu> ucodeadm shows me on 0xa20120a so now I'm confused.
16:44:39 <rmustacc> nahamu: What does psrinfo -vp say about your CPU?
16:44:44 <nahamu> I guess I'm on Zen3
16:44:46 <rmustacc> What specific CPU is it?
16:45:03 <nahamu> AMD Ryzen 7 5800X3D 8-Core Processor
16:45:08 <rmustacc> That's Zen 3, not Zen 2.
16:45:11 <rmustacc> You're not impacted.
16:45:20 <rmustacc> Only Zen 2 is impacted.
16:45:58 <nahamu> Well now I feel really bad for wasting folks' time.
16:46:09 <rmustacc> It's all good, don't worry.
16:46:30 <rmustacc> The microcode revision is going to be processor model specific.
16:46:35 <papertigers> nahamu: you alerted me to zenbleed so it was worth while!
16:46:35 <nahamu> But I learned some things, so thanks everyone.
16:46:42 <rmustacc> So for example, Zen 2 Rome parts (EPYC) is different from Zen 2 client parts.
16:46:43 <nahamu> papertigers: aha, good.
16:53:05 <andyf> papertigers - that tracks with what I just put in https://www.illumos.org/issues/15811
16:53:06 <fenix> → BUG 15811: Update AMD microcode to 20230724 (In Progress)
17:02:21 <andyf> Can we have some links for illumos 15811 please fenix?
17:02:22 <fenix> BUG 15811: Update AMD microcode to 20230719 (In Progress)
17:02:22 <fenix> ↳ https://www.illumos.org/issues/15811 | https://code.illumos.org/c/illumos-gate/+/2970
18:16:31 <nahamu> andyf: does the non-hotload version of loading the microcode persist across reboots, or is this something where to remain safe you must stay on up-to-date versions of illumos (or Linux or whatever)? I just want to be certain before advising anyone else.
18:21:33 <nahamu> andyf: feel free to ignore me:
18:21:35 <nahamu> https://superuser.com/questions/935217/how-is-microcode-loaded-to-processor
18:25:24 <alanc> if you want to be sure you're safe, I believe the best is to get a BIOS/UEFI/motherboard-firmware update that includes the new microcode, so it's there before the OS boots and the OS doesn't have to worry about it/can't fail to update it
18:26:25 <alanc> otherwise I believe OS-loaded microcode updates persist across fast reboots, but not power-cycles/full-resets/"slow" reboots
18:29:32 <nahamu> yup, thanks alanc
21:36:17 <gitomat> [illumos-gate] 15811 Update AMD microcode to 20230719 -- Andy Fiddaman <illumos⊙fn>
21:57:26 <jbk> does fast reboot even work anymore? :)
21:59:01 <richlowe> as well as it ever did
22:00:16 <richlowe> it's increasingly unlikely that it'll happen for you, since xhci(4D) doesn't quiesce
22:00:32 <richlowe> you'll either have to forcibly disable all your usb3, or be on a computer old enough it probably got tested on it.