From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1EA02C2D0C0 for ; Mon, 23 Dec 2019 22:15:08 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 302EE20709 for ; Mon, 23 Dec 2019 22:15:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="slySy+Kz" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 302EE20709 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id B167E1686; Mon, 23 Dec 2019 23:14:14 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz B167E1686 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1577139304; bh=cLd2czgud9ISdm1hWEmYu/C869Vf+q8q9mbf0i+zx08=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=slySy+KzZBc21I7kFj7oyJ0yfx+O7TvmPZQFV6f0NbOzKtD/q4ciLN77byFD9DDJu N1br4RSNMgtkPI5W1PLToFLkhYrshOxwu+DVyQJqYRQhXf3zk1fztLNnej7mK8M2x4 UBp2VQUYWaKnozByEI2jOuC2wXAlsFLLrqbAycUU= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 2B98CF8012F; Mon, 23 Dec 2019 23:14:14 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id E9E97F80130; Mon, 23 Dec 2019 23:14:11 +0100 (CET) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 74936F80087 for ; Mon, 23 Dec 2019 23:14:08 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 74936F80087 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id E4BE8AF2B; Mon, 23 Dec 2019 22:14:07 +0000 (UTC) Date: Mon, 23 Dec 2019 23:14:07 +0100 Message-ID: From: Takashi Iwai To: Klaus Ethgen In-Reply-To: <20191223171833.GA17053@chua> References: <20191207200643.GA10092@ikki.ethgen.ch> <20191208173127.GE4433@ikki.ethgen.ch> <20191209085716.GA12935@ikki.ethgen.ch> <20191210143245.GA30160@ikki.ethgen.ch> <20191210151036.GB23758@ikki.ethgen.ch> <20191223171833.GA17053@chua> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Cc: alsa-devel@alsa-project.org Subject: Re: [alsa-devel] CPU hook snd_hda_intel X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Mon, 23 Dec 2019 18:18:33 +0100, Klaus Ethgen wrote: > > Hi Takashi, > > Am Di den 10. Dez 2019 um 16:19 schrieb Takashi Iwai: > > Could you try the patch below in addition to the previous one? > > The similar trick was applied to the recent Intel chips for the > > unreliable communications, and the same might work for older chips, > > too. > > This patch seemed to have fixed the issue. I didn't see the problem > again since. OK, good to hear. I believe we should apply this workaround for the all Intel chips, then. I'll submit the proper patch now. thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel