-
sjorgebumped my nodes to latest bloody and now seeing
-
sjorgeWARNING: ixgbe0: filed callback (action=0, ret=-1)
-
sjorgenot sure why this is bow showing up, didnt see any changes wrt to ixgbd
-
sjorgeooh more funcky ness
-
sjorgemy linuc bhyve don't boot
-
sjorgeOh boy lots of stuff broken
-
sjorgesudo segfaults for me for example
-
sjorgeNot good
-
nomadso... you're saying you have a bloody mess on your hands?
-
sjorgenomad yes
-
sjorgeDidn't update for a few weeks due to a mix of oncall and super busy at work
-
sjorgeSo though I'd do it before visiting family for the extended weekend
-
sjorgeThat was a mistake
-
sjorgeBut long live beadm, rolled back to the prev be and everything works again
-
sjorge@andyf @hadfl gist.github.com/sjorge/48b11d7aa453846cdb79038a7d70f8b4 is what I managed to capture before reverting, it aint much unfortunately
-
sjorgeBut it looks like some weird memory allocation failure for bhyve ?
-
sjorgeNot sure for sudo
-
sjorgeIt did not drop a core
-
sjorgeDates of the working be omnios-bloody-20230124, the broken one omnios-bloody-20230317
-
sjorgeSo unfortunately a rather big span
-
sjorgeI see a kstat for the bhyve memory resevoir change and a bump in sudo package + a aarch64 fix... but they seem OK t ome