From: Takashi Iwai Subject: Re: RFC: workaround for 'azx_get_response timeout, switching to polling mode...' Date: Fri, 05 Feb 2010 09:13:19 +0100 Message-ID: References: <1265314817.19186.8.camel@maxim-laptop> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.suse.de (cantor.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id 981C21038AE for ; Fri, 5 Feb 2010 09:13:19 +0100 (CET) In-Reply-To: <1265314817.19186.8.camel@maxim-laptop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Maxim Levitsky Cc: alsa-devel List-Id: alsa-devel@alsa-project.org At Thu, 04 Feb 2010 22:20:17 +0200, Maxim Levitsky wrote: > > Hi, > > Although I thought that polling mode is harmless, it sometimes isn't. > I found out that after few dozens of hibernate cycles, the timeout would > happen again kicking out first MSI, and then whole RRIB (single_cmd). > > However, I also found out that if I resend the command that caused the > timeout, it would complete normally. > Even futher, it is possible to poll for this command, and send next > normally. It just works. > So interrupts do work, but sometimes (very rarely) are missed. It might > be even a hardware bug. > > The patch I send allows to delay switch to polling till we get 3 such > timeouts in a row. > > I tested this approach for about 130 hibernate cycles. Thanks! Applied both patches now. I changed snd_printd() to snd_printdd() since the former is enabled on vendor kernels often as default, and this can worry innocent users (I know from my experiences :) Takashi