02:41:52 hi 02:42:13 Targeting illumos based distributions, what's the recommended init system? - OpenRC? - Something else? 03:05:57 smf 03:06:22 see https://illumos.org/man/7/smf 03:08:35 Thanks 03:22:00 how do you switch threads in mdb (on a process core)? i thought maybe ::context but that doesn't seem to be it 03:24:01 I never have. I just use the dcmds to address the thread. 03:24:04 What are you trying to get at? 03:24:17 really just ::stack 03:24:47 ::findstack? 03:25:12 Just like a kernel crash dump. 03:25:29 Just you don't need the ulwp_t address just the thread id. 03:25:41 aha! 03:26:05 And you can do the same ::walk thread | ::stacks, etc. 03:29:26 Let me know if there's other stuff that'd help you out. 05:07:10 Was there another way to fetch the commits hooks from gerrit? scp sjorge⊙cio:hooks/commit-msg .git/hooks doesn't seem to work 05:07:31 I was messing about and messed up my repo just now and delete it and started fresh, but don't have the local copy anymore 05:08:48 got it, rtfm, but the gerrit included one not ours, just a curl from https://code.illumos.org/tools/hooks/commit-msg 05:14:06 Hmm seems I did not mess up my repo and it's something else? I had a `error: remote unpack failed: error badDate: object 8eec3430a514cd7c4e568f6dbe40d81b2f8f2d27: bad date` when pushing the cstyle fixes. I though I messed up git but started fresh and just git apply-patch my changes (so it keeps the commit/change id) but I get the same 17:35:19 jbk: I feel like ::context is supposed to do it though 17:35:27 maybe 17:36:59 that seemed the closest thing, but maybe I wasn't giving it the right thing? 17:37:33 unfortunately its help doesn't really tell you what it's expecting 18:13:34 [illumos-gate] 15735 revamp nvme and disk FMRIs, property groups, and related -- Robert Mustacchi 19:29:29 Note to other distro maintainers: OpenIndiana has problems to build the actual firefox version with binutils-2.41 while 2.40 work fine. So I will go back to 2.40 until this has been sorted out. 19:31:42 Hm, or not: There already seems to be a patch for it according to an email I just got: https://bugzilla.mozilla.org/show_bug.cgi?id=1846703 19:48:56 [illumos-gate] 15711 snoop capture into rotating output files -- Toomas Soome 20:31:40 [illumos-gate] 15832 loader: chain command is really expecting MBR/VBR boot code -- Toomas Soome 22:15:29 rmustacc: if there's a scenario w/ mac where you have > 1 rx ring, but only 1 shared interrupt, is there any harm in having the ring interrupt enable/disable function just do nothing? 22:15:42 the man page suggest those methods are mandatory for rx rings 22:16:43 but in that scenario, it seems like enabling/disabling interrupts in the mc_start/mc_stop method instead 22:16:49 would make more sense 22:17:15 (this is probably a corner case, but wanted to at least try to be reasonable about it) 22:53:34 jinni illumos 15834 22:53:43 jinni illumos#15834 22:53:52 fenix illumos#15834 22:53:53 BUG 15834: Update Intel microcode to 20230808 (New) 22:53:54 ↳ https://www.illumos.org/issues/15834 | https://code.illumos.org/c/illumos-gate/+/3001 22:54:10 (jinni lives on #smartos, my bad.) 23:19:54 jbk: You mean there's no separate interrupt cause register for the rx rings that's separate from the MSI-X? 23:20:23 If you have more than 1 rx ring and you don't have separate interrupt generation for that, then I don't think you should expose multiple rings based on my memory. 23:24:44 There is definitely a problem. We call the interrupt disable path when we come in to poll. 23:27:50 So even if you're going to ignore the interrupts on that ring, polling will happen.