From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752679AbbDDMhY (ORCPT ); Sat, 4 Apr 2015 08:37:24 -0400 Received: from cantor2.suse.de ([195.135.220.15]:58461 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752133AbbDDMhW (ORCPT ); Sat, 4 Apr 2015 08:37:22 -0400 Date: Sat, 04 Apr 2015 14:37:21 +0200 Message-ID: From: Takashi Iwai To: Valdis Kletnieks Cc: Jaroslav Kysela , alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Subject: Re: linux-next - strange audio bug In-Reply-To: <57781.1428021275@turing-police.cc.vt.edu> References: <57781.1428021275@turing-police.cc.vt.edu> 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/24.4 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) 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 Thu, 02 Apr 2015 20:34:35 -0400, Valdis Kletnieks wrote: > > Next-20150310 works OK, next-20150324 has the bug. > > Dell Latitude E6530 laptop, lspci tells me: > > 01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1) > Subsystem: Dell Device 0535 > ... > Kernel driver in use: snd_hda_intel > > Symptoms: Audio works perfectly at boot, and for some amount > of time after. But somewhere around 6-8 hours of uptime, it gets > into a strange state where I'll get no audio... and then it will > cut in for all of 2 seconds or so (fairly consistent, that part), > and then cut back out for anywhere from 10 seconds to a minute, > then another 2 seconds of sound.. lather rinse repeat. > > Before I start the thankless task of bisecting this (which means I'll > be able to do only 1, *maybe* 2 steps a day), does this ring any bells? Try for-next branch of sound git tree git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git Now I merged fixes that might be relevant with the runtime PM on some codecs, so it might work better. In anyway, please give alsa-info.sh outputs at good and bad-working states. thanks, Takashi