From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751506AbbCOIXU (ORCPT ); Sun, 15 Mar 2015 04:23:20 -0400 Received: from cantor2.suse.de ([195.135.220.15]:57075 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751245AbbCOIXQ (ORCPT ); Sun, 15 Mar 2015 04:23:16 -0400 Date: Sun, 15 Mar 2015 09:23:15 +0100 Message-ID: From: Takashi Iwai To: Pavel Machek Cc: perex@perex.cz, alsa-devel@alsa-project.org, kernel list Subject: Re: 4.0-rc3: sound broken in chromium but not in mpg123 In-Reply-To: <20150315081544.GA17650@amd> References: <20150314201109.GA21052@amd> <20150315081544.GA17650@amd> 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 Sun, 15 Mar 2015 09:15:44 +0100, Pavel Machek wrote: > > On Sun 2015-03-15 09:12:47, Takashi Iwai wrote: > > At Sat, 14 Mar 2015 21:11:09 +0100, > > Pavel Machek wrote: > > > > > > Hi! > > > > > > Intel desktop machine: > > > > > > 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High > > > Definition Audio Controller (rev 01) > > > > > > Sound worked ok in both in previous kernel versions. > > > > > > Any ideas? > > > > How broken? Did you get any error messages? > > I get some funny, faint, rhytmic noises where audio should > be... Actually, I somehow suspect something is wrong with time during > video playback. Did you try audio playback without video on chromium? > > If the behavior depends on the application (e.g. ALSA vs OSS), I'd > > suspect rather a device permission problem at first. There are no > > significant changes between 3.19 and 4.0-rc3 regarding HD-audio. > > My system contains pulseaudio, so it is more complex than ALSA vs OSS > :-(. OK, that was missing information :) Then there should be any difference in the kernel driver side -- it's only a single PA process who accesses the sound device in the very same manner no matter what clients are used (after all it's the purpose of PA). > Audio seems to work ok on thinkpad x60 with very very similar config. OK, then another thing I would check is to try different sample rates (e.g. via playing WAV files over PA). Takashi