alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Sound broken (first couple of seconds play looping) on Sony Vaio VPX11S1E (HDA, ALC262)
Date: Thu, 29 Sep 2022 11:05:47 +0200	[thread overview]
Message-ID: <c24d34a9-e609-d44d-8e0f-c2e5928b95f4@redhat.com> (raw)
In-Reply-To: <87y1u290cv.wl-tiwai@suse.de>

Hi,

On 9/29/22 08:10, Takashi Iwai wrote:
> On Wed, 28 Sep 2022 18:33:55 +0200,
> Hans de Goede wrote:
>>
>> Hi,
>>
>> On 9/11/22 09:05, Takashi Iwai wrote:
>>> On Sun, 11 Sep 2022 08:15:59 +0200,
>>> Takashi Iwai wrote:
>>>>
>>>> On Sat, 10 Sep 2022 19:52:36 +0200,
>>>> Hans de Goede wrote:
>>>>>
>>>>> Hi All,
>>>>>
>>>>> To test some kernel work (backlight refactor) which I have been doing
>>>>> I have booted Debian Testing with a 6.0 kernel on a Sony Vaio VPX11S1E
>>>>> (which is ancient).
>>>>>
>>>>> I noticed that when tab-completing something in a terminal the
>>>>> terminal bell sound would keep repeating and playing another longer
>>>>> sound sample gets stuck with the first couple of seconds of that
>>>>> sample looping.
>>>>>
>>>>> This is under GNOME3 with pulseaudio as sound server.
>>>>>
>>>>> I accidentally found an interesting workaround if I run:
>>>>>
>>>>> aplay -Dplughw:CARD=MID,DEV=0 /usr/share/sounds/alsa/Front_Left.wav
>>>>>
>>>>> once, then that works properly and after that the problem is gone...
>>>>>
>>>>> Note that this laptop does have only 1 speaker AFAICT.
>>>>>
>>>>> alsa-info output below.
>>>>>
>>>>> I would be happy to test any patches / module-options which might
>>>>> fix this.
>>>>
>>>> Could you check the very latest Linus tree (6.0-rc5)?
>>>> There has been a regression fix for HD-audio, and possibly this might
>>>> be your case.
>>>
>>> And if this doesn't change the behavior, try snoop=0 option for
>>> snd-hda-intel module.
>>
>> Thanks, I've just tried with 6.0-rc6 both with and without snoop=0
>> and neither helps I'm afraid.
> 
> Then one another thing could be position_fix option of snd-hda-intel.
> Otherwise we need bisection -- supposing it worked well in the past.

Thanks, position_fix=1 does the trick (I did not try any of
the other possible values).

I see there is a snd_pci_quirk position_fix_list, so I guess
I should prepare a patch adding a quirk for this?

Or are some other position_fix values preferred and should
I try those first?

> But as it's a so old laptop, maybe not worth...

Agreed, but it looks like a bisect won't be necessary :)

Regards,

Hans



  reply	other threads:[~2022-09-29  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10 17:52 Sound broken (first couple of seconds play looping) on Sony Vaio VPX11S1E (HDA, ALC262) Hans de Goede
2022-09-11  6:15 ` Takashi Iwai
2022-09-11  7:05   ` Takashi Iwai
2022-09-28 16:33     ` Hans de Goede
2022-09-29  6:10       ` Takashi Iwai
2022-09-29  9:05         ` Hans de Goede [this message]
2022-09-29  9:38           ` Takashi Iwai
2022-10-01 13:36             ` Hans de Goede
2022-10-01 14:20               ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c24d34a9-e609-d44d-8e0f-c2e5928b95f4@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).