From owner-freebsd-current@FreeBSD.ORG Thu Mar 27 07:53:38 2003 Return-Path: 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 B999E37B401; Thu, 27 Mar 2003 07:53:38 -0800 (PST) Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 841A443FBF; Thu, 27 Mar 2003 07:53:36 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: from zibbi.icomtek.csir.co.za (localhost [IPv6:::1]) h2RFrP1F085583; Thu, 27 Mar 2003 17:53:25 +0200 (SAST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.12.8/8.12.6/Submit) id h2RFrOml085582; Thu, 27 Mar 2003 17:53:24 +0200 (SAST) Date: Thu, 27 Mar 2003 17:53:24 +0200 From: John Hay To: Orion Hodson Message-ID: <20030327155324.GA85091@zibbi.icomtek.csir.co.za> References: <3E828F75.1000400@btc.adaptec.com> <200303270749.h2R7nEAT095067@puma.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200303270749.h2R7nEAT095067@puma.icir.org> User-Agent: Mutt/1.4i X-Spam-Status: No, hits=-26.6 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: Scott Long cc: current@freebsd.org Subject: Re: AC97 sound problems with current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2003 15:53:40 -0000 > > | > There is a calibration step in the driver to determine the clock rate of th > | e > | > AC97 link. What you are seeing is the calibration step failing and setting > | a > | > bogus ac97 link rate. I took a cursory look a couple of weeks back and it > | > smelt like the timecounter initialization point changed, but haven't gotten > | > | > around to looking closer and fixing the driver. > > It's definitely nothing to do with the timecounter - quick test on other h/w > along similar lines. I don't access to an ich board to test on - it's > probably obvious, but I'm not seeing it just now with visual inspection... It doesn't look like it is the timecounters. I just added some printfs and it looks like this: pcm0: measured ac97 link rate at 512000000 Hz t1 1.098359, t2 1.098363 ociv 0, nciv 1, bytes 8192 tsc1 445813142, tsc2 445821922, diff 8780 The tsc values are just from rdtsc(), I added tsc1 = rdtsc() just above the first microtime() and tsc2 just after the last. My machine is a 1.8G P4 (ICH2), so the timecounter values seem correct. I have kernel around the middle of Feb that gets the value right and one from March 4 that gets it all wrong. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org