In omacom/omarchy#15950:issuecomment-6358826873, omarchybot traced reported memory-reclaim freezes to an out-of-tree binder_linux module failing to load alongside the kernel's built-in binder. Its analysis found an error path that leaves a memory-reclaim callback registered after module code is freed. The bot reported three worker hangs after attempting the load and none in three control runs without it, although it could not capture the worker's oops text.
hamedtareqhamed supplied another crash report involving firewall logging. omarchybot explained how freed module memory could make the same defect appear inside different networking functions. jhnct subsequently reported that removing the module stopped the observed oopses in omacom/omarchy#15950:issuecomment-6371695054. The issue remains open, and the investigation explicitly did not explain an earlier sighting on kernel 7.2.5-3.
