21:44:01 <sjorge> bumped my nodes to latest bloody and now seeing
21:44:06 <sjorge> WARNING: ixgbe0: filed callback (action=0, ret=-1)
21:44:42 <sjorge> not sure why this is bow showing up, didnt see any changes wrt to ixgbd
22:05:38 <sjorge> ooh more funcky ness
22:05:47 <sjorge> my linuc bhyve don't boot
22:07:28 <sjorge> Oh boy lots of stuff broken
22:07:34 <sjorge> sudo segfaults for me for example
22:07:36 <sjorge> Not good
22:12:49 <nomad> so... you're saying you have a bloody mess on your hands?
22:25:06 <sjorge> nomad yes
22:25:19 <sjorge> Didn't update for a few weeks due to a mix of oncall and super busy at work
22:25:28 <sjorge> So though I'd do it before visiting family for the extended weekend
22:25:30 <sjorge> That was a mistake
22:25:43 <sjorge> But long live beadm, rolled back to the prev be and everything works again
22:26:02 <sjorge> @andyf @hadfl https://gist.github.com/sjorge/48b11d7aa453846cdb79038a7d70f8b4 is what I managed to capture before reverting, it aint much unfortunately
22:26:14 <sjorge> But it looks like some weird memory allocation failure for bhyve ?
22:26:33 <sjorge> Not sure for sudo
22:26:36 <sjorge> It did not drop a core
22:30:23 <sjorge> Dates of the working be omnios-bloody-20230124, the broken one omnios-bloody-20230317
22:30:34 <sjorge> So unfortunately a rather big span
22:39:26 <sjorge> I see a kstat for the bhyve memory resevoir change and a bump in sudo package + a aarch64 fix... but they seem OK t ome