From owner-freebsd-current Wed Feb 26 13: 3:30 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8C3537B401 for ; Wed, 26 Feb 2003 13:03:28 -0800 (PST) Received: from ion.gank.org (ion.gank.org [198.78.66.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F31943F75 for ; Wed, 26 Feb 2003 13:03:27 -0800 (PST) (envelope-from craig@xfoil.gank.org) Received: from [192.168.69.95] (dsl081-113-221.dfw1.dsl.speakeasy.net [64.81.113.221]) by ion.gank.org (GankMail) with ESMTP id C78F62C5A2 for ; Wed, 26 Feb 2003 15:03:26 -0600 (CST) Subject: Hyperactive ICH2 sound (with workaround) From: Craig Boston To: freebsd-current@freebsd.org Content-Type: text/plain Organization: Message-Id: <1046293382.568.16.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 26 Feb 2003 15:03:03 -0600 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On a recently compiled current the sound from an Intel 82801BA integrated sound chip seems to be accelerated (high pitched and too fast). While it's amusing to listen to certain songs this way, I don't think it should be the default mode of operation ;) Relevant dmesg output: pcm0: port 0xdc40-0xdc7f,0xd800-0xd8ff irq 10 at device 31.5 on pci0 pcm0: pcm0: measured ac97 link rate at 512000000 Hz and sysctl hw.snd.pcm0: hw.snd.pcm0.buffersize: 16384 hw.snd.pcm0.vchans: 0 hw.snd.pcm0.ac97rate: 48000 Here is the output from another system with the same hardware running 5.0-RELEASE: pcm0: port 0xcc40-0xcc7f,0xc800-0xc8ff irq 10 at device 31.5 on pci0 pcm0: measured ac97 link rate at 55939 Hz and the sysctl: hw.snd.pcm0.buffersize: 16384 hw.snd.pcm0.vchans: 4 hw.snd.pcm0.ac97rate: 55939 So it looks like the AC97 link rate measurement isn't working right. Manually setting it with "sysctl hw.snd.pcm0.ac97rate=55939" seems to correct the problem. Current from about a week ago was working fine. A kernel from last night exhibits this problem, as does one cvsupped this morning. I'll go trawling through CVS when I have some free time. Not really a big deal, just wanted to make sure somebody was aware of the problem and also to get the workaround into the mailing list archives... Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message