On Thu, Jul 19, 2018 at 11:24:16AM +0300, Leonid Bobrov wrote: > From: Alexandre Ratchov <[email protected]> > > On Sun, Jul 15, 2018 at 06:40:54AM +0300, Leonid Bobrov wrote: > > > > The diff I use is initial one: > > https://marc.info/?l=openbsd-ports&m=152807586927014&w=2 > > > > ratchov@'s sndio backend is not ready yet, plus I'm afraid to keep > > testing it, because that made kernel panic, after that panic I > rebooted > > with corrupted FFS (I should read about sending bug reports). > > > > Please let me know what doesn't work, including steps to reproduce the > problem. If the problem is specific to your machines, at least provide > a stack trace. > > The kernel crashes you mentioned (unrelated to openal) and are very > important to fix, see sthen@ suggestion on how to handle them. > > Note that the diff I sent doesn't affect the playback direction, so > verifying that it doesn't cause regressions would help as well. > > The steps to reproduce are: install net/toxic, install your latest diff > to audio/openal: > https://marc.info/?l=openbsd-ports&m=152817852312699&w=2 > > Then start Toxic > $ toxic > and make audiocall to anybody. If you don't have contacts to test > audiocall, add echobot to your contact list: > /add [email protected] > Wait few seconds, switch to buffer with echobot and use: > /call > Then when you're done testing audio input, end audio call: > /hangup > And that'll lead to segmentation fault. >
thanks, that's useful. > There is a chance to catch kernel panic when testing audio call in > Toxic with your diff to audio/openal, before I report to bugs@ I have > to read FAQ first, then get yet another kernel panic. I should have a > backup machine tomorrow so I won't have to worry about my personal data > being lost when FFS will corrupt again thanks to panic. that'd be useful starting point to analyse the kernel crash as well.
