Bug#635362: linux-image-3.0.0-1-amd64: HDA intel: choppy sound on 3.0
Le 26/07/2011 11:27, Jonathan Nieder a écrit :
> Colomban Wendling wrote:
>
>> [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
>> [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
>> [ 0.000000] ------------[ cut here ]------------
>> [ 0.000000] WARNING: at /build/buildd-linux-2.6_2.6.39-3-amd64-wlUGAK/linux-2.6-2.6.39/debian/build/source_amd64_none/drivers/pci/dmar.c:634 warn_invalid_dmar+0x77/0x85()
>> [ 0.000000] Hardware name: MS-7636
>> [ 0.000000] Your BIOS is broken; DMAR reported at address fed93000 returns all ones!
>> [ 0.000000] BIOS vendor: American Megatrends Inc.; Ver: V1.1; Product Version: 1.0
>
> Unrelated BIOS bug, presumably.
Yeah, I never investigated this but it never shown any actual
consequences -- and anyway it is in both kernel, working and not so I
guess it has no impact on this very problem.
Though, I should definitely try to fix this, that's true.
>> [ 71.284844] hda-intel: Invalid position buffer, using LPIB read method instead.
>
> This is from sound/pci/hda/hda_intel.c, with the condition
>
> if (!pos || pos == (u32)-1) {
>
> I think maks looked at this codepath recently, for example to apply
>
> commit a810364a
> Author: Takashi Iwai <tiwai@suse.de>
> Date: Tue Jun 7 12:23:23 2011 +0200
>
> ALSA: hda - Handle -1 as invalid position, too
>
> When reading from the position-buffer results in -1, handle as it's
> invalid and falls back to LPIB mode as well as 0.
>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>
> The message only appears in the bad log, so I guess pos is -1.
I've tried to printk() the value of pos yesterday for that very reason
(I checked a bit of history of that file), and it looked like it is 0,
not -1. However, I haven't tried to revert that patch that also moves
the check.
> There have been other changes to the driver recently, too. If you have
> time for it, could you try pristine v3.0 (which lacks that patch) or
> the latest snapshot (which includes it and some other fixes on top)
> from kernel.org, following the instructions from [1] and if it fails,
> report the results to alsa-devel@alsa-project.org, cc-ing Takashi Iwai
> and this bug?
I tried both mainline and git snapshot, and bot shown the problem.
Though, in mainline there is nothing in the logs. I'll then post to
alsa-devel as you suggested.
Regards,
Colomban
Reply to: