01:18:55 <rzezeski> jbk: okay, I misread my own code earlier, it makes sure not to run any HW emulation if the underlying part supports it, which I verified with a local setup and some dtrace. However, that code still should have been removed as part of the unwinding of OS-6778, but it's technically not hurting anything.
01:19:19 <rzezeski> The reason you hit this gets back to the other issue I was talking about. Where a packet is coming down with HW flags which it shouldn't have
01:22:43 <jbk> hmm.. i wonder how hard it'd be to figure out what's going on with that.. it's a separate issue to the thing I'm actually trying to work on...
01:23:16 <rzezeski> I understand, I don't know if it's a configuration people ever have: multiple NICs on same subnet with differing hardware offloads
01:23:30 <rzezeski> I can replicate such a setup locally, so I might see if I can replicate
01:25:38 <rzezeski> jbk: `dtrace -qn 'e1000g_retrieve_context:return { @[arg1 ? "true" : "false"] = count(); }'`
01:25:47 <rzezeski> with the assert remove you should see that return false sometimes
01:26:12 <rzezeski> assuming you still do the SSH over e1000g0 and do something on the terminal to warrant SSHD sending an LSO segment
01:40:42 <nahamu> bahamat: https://github.com/fsnotify/fsnotify/issues/12 is finally marked closed! Not sure if you still use telegraf, but if you are, perhaps improvements are finally unblocked?
02:03:28 <bahamat> Sweet!
02:03:52 <bahamat> Not at MNX, but I think Joyent still does.
02:04:24 <bahamat> But we do use prometheus, and it also uses fsnotify, so that'll be great for us.
08:01:03 <vtorri> hello
08:01:41 <vtorri> I tried to compile pkgconf and I got warnings saying that strdup() is not declared
08:01:47 <vtorri> according to this man page:
08:02:20 <vtorri> https://linux.die.net/man/3/strdup
08:02:26 <vtorri> strdup() is POSIX
08:03:00 <vtorri> but in string.h, I see, like other functions, no POSIX guard , but __EXTENSIONS__
08:03:10 <vtorri> is it normal ?
15:30:02 <gitomat> [illumos-gate] 15077 ficl: make sure the loader emulator does set console -- Toomas Soome <tsoome⊙mc>
15:31:45 <toasterson> vtorri: looks like you are not setting up the correct C macro guards. Extensions is a special macro being defined with C99 flag I think but people here can elaborate which one you need.
15:44:25 <gitomat> [illumos-gate] 15063 vmm: cast to smaller integer type 'boolean_t' from 'void *' -- Toomas Soome <tsoome⊙mc>
15:47:38 <gitomat> [illumos-gate] 15027 The ls command should show SIDs instead of ephemeral IDs -- Gordon Ross <gwr⊙rc>
16:31:11 <gitomat> [illumos-gate] 15059 Update AMD microcode to 20220930 -- Andy Fiddaman <illumos⊙fn>
17:01:05 <nikolam> Are AMD CPUs still without illumos KVM/bhyve support
17:04:08 <danmcd> I know for certain AMD Zen and later works FINE on BHYVE using a modern build.
17:04:21 <danmcd> There may be more, but I'll defer to others for those details.
17:09:06 <nahamu> I run SmartOS on a Ryzen 5700G and BHYVE works just fine.
17:24:12 <jbk> hasn't AMD support for bhyve always been there since bhyve support was added?
17:24:24 <nahamu> I think so.
18:03:01 <nikolam> Aaand soo, preferred hardware section on wiki for SmartOS AND Triton.. needs update to mention.. AMD works just fine for Bhyve..?
18:05:53 <jperkin> yes, even works great on my old crappy N36L
18:20:09 <jclulow> jperkin: I finally figured out how to bust up a JDK so that I could use the remote access card in my N36L haha
18:20:20 <jclulow> You have to turn of all the TLS safeties
18:21:14 <andyf> jbk - yes, it's only bhyve PCI pass-through which is not available on AMD as far as I know
18:43:42 <danmcd> Who needs TLS safety anyway, right?
18:44:41 <danmcd> Gonna take a long-shot here, but does anyone have experience with AMD X470 chipsets spontaneously power-cycling after heavy SATA load (like "zpool scrub" on a 14TB mirror load)?
18:45:47 <danmcd> It's gotten LESS shitty with a BIOS upgrade in 2021, but it still happens 1/2 the time I think.  And NO idea what's doing it.  (I'm tempted to unplug it from power, re-plug, and try again, thinking it might be some insufficient BIOS-level counter.)
18:46:45 <danmcd> And now, with consistency,  right before the powercycle:  
18:46:46 <danmcd> ahci: [ID 517647 kern.warning] WARNING: ahci0: watchdog port 6 satapkt 0xfffffeb305ba9b18 timed out
18:49:47 <jperkin> jclulow: ah nice, I didn't bother getting that, is it one that needs a license to work too?
18:50:37 <jbk> danmcd: let me see if we've upstreamed all of our relevant fixes yet
18:51:08 <jbk> IIRC, the deadlock was fixed (though unlikely to hit that from a scrub.. taht was caused by out extensive use of 'artisinal SCSI packets' :P)
18:51:21 <danmcd> jbk you think it's an illumos problem?  I can understand it might be because my dump device is on the very (big) drives being scrubbed.
18:51:49 <jbk> there were some questionable bits with how timeout/reset handling was being done in the sata driver
18:51:59 <jbk> i need to look to see the specifics
18:52:11 <jbk> if they could potentially be involved
18:55:53 <jbk> yeah.. i think there's a deadlock in sata_hba_event_notify.. we have a fix that farms some bits out to a taskq (it's not ideal, but better)
18:56:39 <jbk> i'll try to get details in a bit once I can hopefully get this otehr stuff i'm working on finished
18:58:20 <danmcd> I may try and repartition my SSDs to have 128GB less unassigned space, and make those mirrored slices the "dump" pool whose only job is to be the dump device.
18:58:39 <jbk> nvme?
18:58:41 <danmcd> (I do Weird Things with my SSDs...)
18:58:46 <danmcd> No, SATA.
18:59:09 <danmcd> Hand-me-downs that were new, but outlasted the kids' laptops they were installed in.  :upside_down:
18:59:30 <danmcd> Pair of these:
18:59:30 <danmcd>        0. c10t2d0 <Samsung-SSD 860 EVO 500GB-RVT02B6Q-465.76GB> 
19:00:44 <jbk> at least with the deadlock that I (finally) found.. one of the complications was that it locked up the sata framework enough that dumps wouldn't work to sata disks (which is arguably a bug, but haven't been able to dig into that)
19:01:00 <danmcd> Oof.
19:01:14 <danmcd> My symptoms were BLINK power gone.
19:01:27 <jbk> oh that i haven't seen
19:01:30 <danmcd> I even put a video camera when I was able to reproduce it and NOTHING.
19:01:52 <danmcd> I need to restore my reddit because the only community with my mobo with any activity appears to be there.
19:02:14 <danmcd> https://www.asrockrack.com/general/productdetail.asp?Model=X470D4U
19:03:18 <danmcd> The only complaint I have is that scrubbing (and also `zfs send -r` -ing) my 14TB mirrored pool (which is slightly less than half full right now) tickles this power-flicker thing.
19:03:24 <danmcd> Builds don't do it.
19:03:34 <danmcd> (I wonder if THAT's because those write to slog?)
19:20:41 <rmustacc> Dan is there anything in the ipmi log by chance?
19:22:21 <danmcd> Lemme check again, but last time(s) there weren't, just "power on".
19:30:46 <mxshift> A lot of AM4 boards had VRMs that only barely meet the minimum requirements for Zen3
19:34:03 <danmcd> I'm running Zen2, FWIW.
19:34:15 <danmcd> @rmustacc https://kebe.com/~danmcd/webrevs/ipmi-log.png
19:34:39 <danmcd> Looks like power-off pair followed by power-on pair.
19:36:29 <danmcd> I've got "raw data" too, but that corresponds to reading my mobo manual, so that's on me.
19:45:20 <danmcd> Actually, no need.  The ones above match reboot times to the T.
20:01:04 <gitomat> [illumos-gate] 15032 SMB: Can't create a file with a NULL DACL -- Matt Barden <mbarden⊙tc>
20:04:03 <danmcd> (The codes I'm seeing from the power-flicker match ones from me typing "reboot".)
20:07:30 <rmustacc> That's unfortunate. the things that would come to mind that lead there that a colleague hit recently were due to a failing fan and thermal trip.
20:07:34 <rmustacc> But I'd hope things like ipmi would do that.
20:09:16 <danmcd> "Thermal problems" *is* on my list of possibilities.  My case is, unfortunately, not well suited for two disks like that to be so close to each other.  I think it need a sufficiently long time to heat, though, and I've contemplated upping the fan count in there, or even replacing the case with a different one better suited to space between drives.
20:09:30 <danmcd> s/need/needs/
20:10:45 <rmustacc> There case was due to a failed fan, so that seems less likely here.
20:46:59 <gitomat> [illumos-gate] 15050 SMB server mishandles some SIDs -- Matt Barden <mbarden⊙tc>
22:22:43 <AmyMalik> I have LWPs on the brain.
22:29:22 <jbk> at least they're lightweight :P
22:30:16 <AmyMalik> jbk: eh
22:31:59 <AmyMalik> I specifically have the matter of "how do i make a thread-unsafe greenthreads system-thread-safe" on the brain
22:42:04 <jclulow> one big mutex
22:43:45 <rzezeski> Erlang
22:43:53 * rzezeski ducks
22:44:15 <rzezeski> that was for your arekinath
22:45:34 <arekinath> I feel like the BEAM answer to "how do I make it system-thread-safe" is "add more threads"
22:45:47 <arekinath> which is intuitively crazy but seems to somehow work
22:46:25 <arekinath> but also those people took too many puffs on the macro pipe
22:46:41 <rzezeski> Rickard Green keeps your green threads safe
22:47:10 <rzezeski> when all you have is a mailbox, everything is a message
22:47:45 <AmyMalik> jclulow, that's called a giant lock
22:48:18 <AmyMalik> arekinath, I mean...
22:48:23 <jclulow> Who would win in a fight, though, one giant lock or a giant pile of little locks
22:49:15 <rzezeski> what if, hear me out, you have one giant lock to keep track of the little locks
22:49:18 <arekinath> the giant pile of little locks really know how to kill you dead(lock)
22:49:56 <AmyMalik> bah
22:52:11 <AmyMalik> https://en.wikipedia.org/wiki/Giant_lock
22:52:56 <jclulow> TIL
22:54:18 <arekinath> programs with giant locks are considerably shorter than programs with fine-grained locking. here is a driver in 4.4BSD. and here is the equivalent driver in Linux
22:54:27 <yuripv> and some system are on crusade to eliminate it, e.g. WARNING: Device "psm" is Giant locked and may be deleted before FreeBSD 14.0.
22:55:08 <arekinath> it's the Bananarama of concurrency primitives
22:57:48 <AmyMalik> hm
22:58:45 * danmcd shouldn't *monitor* this situation too closely.
22:59:47 <arekinath> I think the word you're after is supervise, danmcd
23:00:03 <arekinath> but you can spell it with a Z if you really want
23:00:09 <arekinath> the compiler will accept it
23:03:26 <danmcd> Sorry about that, I was dining with some philosophers earlier. (Now I have to leave... seriously.)
23:03:44 <jbk> and dodge the produce? :)
23:07:00 <AmyMalik> ¿_?
23:10:05 <rzezeski> danmcd ran off with all the forks and now the rest of us must starve
23:12:36 <arekinath> does that make him a Byzantine fork thief or something
23:14:37 <rzezeski> I hear he ran off to the Island of Paxos
23:16:49 <AmyMalik> this is some concurrent programming joke I don't understand, init?
23:18:47 <AmyMalik> Diabolical algorithms: a reader-writerS lock. In this algorithm, there may only be one reader at a time, but there may be any number of writers. I can't imagine this being useful for anything except efficiently, cleanly and quickly causing severe data corruption.