From: Maxim Levitsky Subject: RFC: workaround for 'azx_get_response timeout, switching to polling mode...' Date: Thu, 04 Feb 2010 22:20:17 +0200 Message-ID: <1265314817.19186.8.camel@maxim-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-bw0-f221.google.com (mail-bw0-f221.google.com [209.85.218.221]) by alsa0.perex.cz (Postfix) with ESMTP id 266D610384B for ; Thu, 4 Feb 2010 21:20:22 +0100 (CET) Received: by bwz21 with SMTP id 21so2578843bwz.4 for ; Thu, 04 Feb 2010 12:20:20 -0800 (PST) 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: alsa-devel Cc: Takashi Iwai List-Id: alsa-devel@alsa-project.org 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. Best regards, Maxim Levitsky