From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755864AbYD2Nkm (ORCPT ); Tue, 29 Apr 2008 09:40:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759248AbYD2NkW (ORCPT ); Tue, 29 Apr 2008 09:40:22 -0400 Received: from mx1.suse.de ([195.135.220.2]:46354 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758315AbYD2NkV (ORCPT ); Tue, 29 Apr 2008 09:40:21 -0400 Date: Tue, 29 Apr 2008 15:40:19 +0200 Message-ID: From: Takashi Iwai To: Jan Engelhardt Cc: Linux Kernel Mailing List Subject: Re: sound: azx_get_response timeout In-Reply-To: References: User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta28) (fuki) (+CVS-20070806) (i386-suse-linux) 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 Tue, 29 Apr 2008 14:38:27 +0200, I wrote: > > > >> The only way to get rid of the GETOSPACE=0 state is to reboot the > > >> machine. Say, could this be due to the crappy VIA hardware? > > > > > >Possible. > > > > > >You may try some module options for snd-hda-intel, > > >e.g. position_fix=0. See ALSA-Configuration.txt. > > > > No change. > > Then I have no certain clue what could be a culprit yet now. The > symptom sounds like the DMA stops working by any reason, but this is a > pretty uncommon case. Usual hda-intel bugs are about the wrong mixer > setting or routining, or the communication errors between the > controller and the codec chips. You'd have to see other error > messages in such cases. > > It might be related with the power management... And I should have asked this before all -- is it a regression? Takashi