From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752683Ab2AHKLW (ORCPT ); Sun, 8 Jan 2012 05:11:22 -0500 Received: from cantor2.suse.de ([195.135.220.15]:40500 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751512Ab2AHKLV (ORCPT ); Sun, 8 Jan 2012 05:11:21 -0500 Date: Sun, 08 Jan 2012 11:11:19 +0100 Message-ID: From: Takashi Iwai To: "Artem S. Tashkinov" Cc: linux-kernel@vger.kernel.org, perex@perex.cz, alsa-devel@alsa-project.org Subject: Re: ALSA regression in recent kernels: Intel HDA/ALC892 sound glitches In-Reply-To: <162622243.549273.1326016167416.JavaMail.mail@webmail13> References: <1253360187.305758.1325762980205.JavaMail.mail@webmail07> <162622243.549273.1326016167416.JavaMail.mail@webmail13> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Sun, 8 Jan 2012 09:49:27 +0000 (GMT), Artem S. Tashkinov wrote: > > > On Jan 8, 2012, Takashi Iwai wrote: > > > > At Thu, 5 Jan 2012 11:29:40 +0000 (GMT), > > Artem S. Tashkinov wrote: > > > > > > Hello, > > > > > > Since kernel 3.0.11 I have quite terrible sound artifacts - random pops, clicks and > > > short pauses (~500ms). Linux kernel 3.0.0 is *bug free*. So, some some of patches in > > > kernel *3.0.11* broke the driver, the bug is, of course, present in kernels 3.1 and 3.2. > > > > Could you give alsa-info.sh output to check more details? > > Also, any chance to identify which 3.0.x release breaks the things? > > alsa-info output was attached to my original mail posted into LKML, please check out > you e-mail client. Ah, OK, I'll check it later. I'm still on vacation so I can't check in details. > There are so few changes in Intel/Realtek HDA ALSA code between 3.0 and 3.0.11 > I thought you could identify the culprit just by looking at the list. Well, it's not too easy since the problem isn't deterministic. You can check the patches with ALSA: hda (or capital) and ALSA: pcm prefix. > ALSA: fm801: Fix double free in case of error in tuner detection > ALSA: fm801: Gracefully handle failure of tuner auto-detect > ALSA: HDA: Add new revision for ALC662 > ALSA: hda - Add position_fix quirk for Dell Inspiron 1010 > ALSA: hda - Add support for 92HD65 / 92HD66 family of codecs > ALSA: HDA: Add support for IDT 92HD93 > ALSA: HDA: Cirrus - fix "Surround Speaker" volume control name > ALSA: HDA: conexant support for Lenovo T520/W520 > ALSA: hda - Disable power-widget control for IDT 92HD83/93 as default > ALSA: hda - Don't add elements of other codecs to vmaster slave > ALSA: hda - Fix ADC input-amp handling for Cx20549 codec > ALSA: HDA: No power nids on 92HD93 > ALSA: hda/realtek - Avoid bogus HP-pin assignment > ALSA: hda/realtek - Fix auto-mute with HP+LO configuration > ALSA: hda/realtek - Skip invalid digital out pins > ALSA: hda - Remove bad code for IDT 92HD83 family patch > ALSA: pcm - fix race condition in wait_for_avail() > ALSA: ua101: fix crash when unplugging > ALSA: usb-audio: Check for possible chip NULL pointer before clearing probing flag > ALSA: usb-audio - Check the dB-range validity in the later read, too > ALSA: usb-audio - clear chip->probing on error exit > ALSA: usb-audio - Fix the missing volume quirks at delayed init > > If you have no ideas about which patch could have broken things, I will try to figure it out > by bisecting. That'll be helpful. thanks, Takashi