At Tue, 15 Jan 2008 15:21:36 -0500, Andrew Paprocki wrote: > > I'm seeing these messages show up in dmesg every once in a while. If > anyone has ideas as to why I'd be seeing these, I can help track down > any potential problems. I am having problems where ALSA playback > stutters while using the OSS-compatibility layer for ALSA works fine > with no stuttering. > > After inserting the module w/ model=6stack-dig: > > ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16 > hda_intel: azx_get_response timeout, switching to polling mode: last > cmd=0x225f0d00 > hda_intel: azx_get_response timeout, switching to single_cmd mode: > last cmd=0x225f0d00 This is scary. It's likely that the codec chip is screwed up after the driver sends an invalid command. > ACPI: PCI Interrupt 0000:01:05.2[B] -> GSI 19 (level, low) -> IRQ 18 > hda-intel: Invalid position buffer, using LPIB read method instead. > > After inserting the module w/ no model defined: > > ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16 > hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... > ACPI: PCI Interrupt 0000:01:05.2[B] -> GSI 19 (level, low) -> IRQ 18 > hda-intel: Invalid position buffer, using LPIB read method instead. The switching to LPIB read is another workaround for some hardwares that don't work with the position buffer. It should be harmless. In doubt, you can try some different position_fix parameters. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
