search for: pcm_open_module

...:01] INFO input-pcm/pcm_close_module Closing PCM input module [2003-11-26 00:00:01] DBUG input/open_next_input_module checking module 1 <p>... [2003-11-26 00:00:01] WARN input/open_next_input_module restarted input within 2 seconds, it probably failed [2003-11-26 00:00:01] INFO input-pcm/pcm_open_module Retrieving PCM to skip [2003-11-26 00:00:01] INFO input-pcm/pcm_open_module Retrieving PCM from standard input [2003-11-26 00:00:01] DBUG input-pcm/pcm_read metadata updates flagged [2003-11-26 00:00:01] INFO input-pcm/pcm_read No more data available [2003-11-26 00:00:01] INFO input/input_loop...

...03-11-25 10:45:51] DBUG input-pcm/pcm_initialise_module Module PCM using buffers of 4096 samples [2003-11-25 10:45:51] DBUG input/initialise_input_modules Module 1 (pcm) has 20 buffers [2003-11-25 10:45:51] DBUG input/open_next_input_module checking module 1 [2003-11-25 10:45:51] INFO input-pcm/pcm_open_module Retrieving PCM to skip [2003-11-25 10:45:51] INFO input-pcm/pcm_open_module Retrieving PCM from standard input [2003-11-25 10:45:51] DBUG input-pcm/pcm_read metadata updates flagged [2003-11-25 10:45:51] WARN metadata/metadata_thread_signal Failed to open file (null) for metadata update: ~<D0...

Hello, I will take your last version, but I have fresher news about the bug that occurs every mornings in fact... I think this is ntpdate which is causing the problem, as the time of the machine change for more than one second. Here is all the info: 09:46:17 up 1 day, 1:22, 2 users, load average: 0.60, 0.71, 0.68 86 processes: 84 sleeping, 2 running, 0 zombie, 0 stopped CPU states: 10.4%