Hi, I have been testing the stability of the jack modules. I am running git pulled from yesterday. pulseaudio 0.9.16-test4-7-gaa74 I have come across this segfault printed to dmesg after pulseaudio falls over: ALSA sound/pci/hda/hda_intel.c:1101: Too big adjustment 32: adj=128, bytes=128, size=4096, periods=32 ALSA sound/pci/hda/hda_intel.c:1101: Too big adjustment 32: adj=128, bytes=128, size=4096, periods=32 ALSA sound/pci/hda/hda_intel.c:1101: Too big adjustment 32: adj=128, bytes=128, size=4096, periods=32 ALSA sound/pci/hda/hda_intel.c:1101: Too big adjustment 32: adj=128, bytes=128, size=4096, periods=32 ALSA sound/pci/hda/hda_intel.c:1101: Too big adjustment 32: adj=128, bytes=128, size=4096, periods=32 ALSA sound/pci/hda/hda_intel.c:1101: Too big adjustment 32: adj=128, bytes=128, size=4096, periods=32 ALSA sound/pci/hda/hda_intel.c:1101: Too big adjustment 32: adj=128, bytes=128, size=4096, periods=32 ALSA sound/pci/hda/hda_intel.c:1101: Too big adjustment 32: adj=128, bytes=128, size=4096, periods=32 pulseaudio[25488]: segfault at 7fc38418348d ip 00000032bf2094f4 sp 00007fc383f80d88 error 4 in libjack.so.0.0.28[32bf200000+11000] How should I go about tracing it? It doesn't take down jack on my system but others have reported issues with massive spikes in CPU load, lockups and jack being brought down. PS, please cc me on the reply. -- Patrick Shirkey Boost Hardware Ltd
