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 9265EC43603 for ; Tue, 10 Dec 2019 14:45:49 +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 1349D20637 for ; Tue, 10 Dec 2019 14:45:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="NoUx7HSr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1349D20637 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 6BA4E1699; Tue, 10 Dec 2019 15:44:57 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 6BA4E1699 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1575989147; bh=b0cgbTCJ+/7kg77IeUnNnQrNqka+XupaT5iyrMhXVx4=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=NoUx7HSr8VO2GGthdM9iRj4F3Cn0Qnn4bgrxaDRUdrYcJhZhu6EXFurzdR5Gcvuar oPzFpWzu/B9znEyWBrCt3HylMiwIvXUOmKRfd/LLXczz0i/XUAWap5iL6dng5iSbvT BckMNEaSKVmJFDFTZyu+cIl3wu9TVn4ELSRi2b9k= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 45118F80268; Tue, 10 Dec 2019 15:43:17 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 7CDFEF80269; Tue, 10 Dec 2019 15:43:15 +0100 (CET) Received: from mx1.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 EF34DF80265 for ; Tue, 10 Dec 2019 15:43:12 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz EF34DF80265 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 5FA88ABC6; Tue, 10 Dec 2019 14:43:12 +0000 (UTC) Date: Tue, 10 Dec 2019 15:43:12 +0100 Message-ID: From: Takashi Iwai To: Klaus Ethgen In-Reply-To: <20191210143245.GA30160@ikki.ethgen.ch> <20191210143543.GA30935@ikki.ethgen.ch> References: <20191202184759.GB29478@ikki.ethgen.ch> <20191207200643.GA10092@ikki.ethgen.ch> <20191208173127.GE4433@ikki.ethgen.ch> <20191209085716.GA12935@ikki.ethgen.ch> <20191210143245.GA30160@ikki.ethgen.ch> 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 Tue, 10 Dec 2019 15:32:45 +0100, Klaus Ethgen wrote: > > Hi Takashi, > > Unfortunately it is not successful. See the attached output of perf. > > There is also a issue with a swapper thread in ath9k code but the one > with the biggest CPU hook is still alsa. Do you see the relevant kernel messages, e.g. switch to polling mode? If that happens, it means that the communication with the chip got broken by some reason. And... On Tue, 10 Dec 2019 15:35:44 +0100, Klaus Ethgen wrote: > > Let me add that this time I encountered the issue after taking the > laptop from the docking station. ... this can be the cause: the hardware doesn't react to the pin jack sense request for the dock that isn't present any longer. Or something goes wrong here, repeating, etc. > After sending it to sleep and waking it up again, the problem is gone > (as it often can be solved). So the problem is very likely some flaky hardware response. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel