Concerning that problem, after a reboot the problem has reoccured two days later:
Oct 17 14:16:09 hostname kernel: [192087.249165] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 17 14:22:08 hostname kernel: [192447.072018] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 17 14:22:38 hostname kernel: [192477.062967] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 17 14:23:06 hostname kernel: [192504.918440] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 17 14:23:37 hostname kernel: [192535.594196] ALSA hda_intel.c:1187: Too big adjustment 32
Uploaded new alsa-info.sh data from the machine: http://www.alsa-project.org/db/?f=e7e696254df6f61fa5e4755e9d1d06403dacf144
Upgrading from alsa-driver-20091005 to alsa-driver-20091017 and will let you know how it worked.
On Wed, Oct 14, 2009 at 9:04 AM, Aleksander Adamowski alsa@olo.org.pl wrote:
After running for almost ten days with alsa-driver-20091005, I didn't observe that problem.
However, a new one (well, one with slightly different symptoms) has surfaced.
The difference is only in the log files. During a Skype conversation, the other side has stopped hearing us; after trying to record some sound with arecord, I got an empty stream (a 44 byte WAV file with only a header) - just like previously.
However, this time there were no messages in the kernel logs whatsoever - no "azx_get_response timeout", no "Suggest a bigger bdl_pos_adj". Arecord also didn't flood the console with overrun errors - it was completely silent apart from the fact that it did not record anything.
The only hda-related entries I saw in the kernel log were a couple hours earlier at 20:44 - while the failure has occured between 23:00 and 00:00.
At 20:44 the following has been logged:
Oct 13 20:44:25 hostname kernel: [117828.065069] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 13 20:44:25 hostname kernel: [117828.073562] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 13 20:44:25 hostname kernel: [117828.083367] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 13 20:44:25 hostname kernel: [117828.578958] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 13 20:44:25 hostname kernel: [117828.584872] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 13 20:44:25 hostname kernel: [117828.592909] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 13 20:44:25 hostname kernel: [117828.651513] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 13 20:44:25 hostname kernel: [117828.657009] ALSA hda_intel.c:1187: Too big adjustment 32 Oct 13 20:44:25 hostname kernel: [117828.665794] ALSA hda_intel.c:1187: Too big adjustment 32
The machine is currently still in the failed state - I cannot record anything until I reboot.
-- Best Regards, Aleksander Adamowski http://olo.org.pl