This is caused by macOS 12 Monterey. Having the same problem, but seeing reports from Intel Mac’s as well.
> That’s extremely similar to the MacBook Pro and Monterey issues I’ve read this week—except I’m still running Big Sur.
Maybe there is more than one issue here, but Intel users having the same issue on Monterey where they did not have it before seems telling. Maybe M1 machines had a different OS build or features that caused this issue in Big Sur and now it's universal in Monterey?