At Wed, 27 May 2020 13:19:22 +0000, nia wrote: > I think this is because audio_rmixer_start is used unguarded > in audio_open (it doesn't check for the sc_rbusy flag). > This isn't the case for pmixer. > > So, if the audio device is opened for recording for the > first time after system resumption, a panic will occur > due to an assertion failure (the recording mixer would > already be busy).
It's because your change didn't restore [pr]mixer's running state correctly. I have fixed it. Thanks, --- Tetsuya Isaki <is...@pastel-flower.jp / is...@netbsd.org>
