linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: lkml <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5.73-mm2 - odd audio problem, bad intel8x0/ac97 clocking.
Date: 30 Jun 2003 17:25:48 -0700	[thread overview]
Message-ID: <1057019147.28319.367.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <200306282131.h5SLVjGk001833@turing-police.cc.vt.edu>

On Sat, 2003-06-28 at 14:31, Valdis.Kletnieks@vt.edu wrote:
> 2.5.73-mm1 is fine.
> 
> This is *not* the "clock runs really really fas"t issue - I left -mm2 running overnight and
> in some 8 hours the system clock only drifted a few seconds versus wall clock (and it's
> possible it was off a few seconds when it booted, as it didn't get an NTP sync at boot).
> 
> Audio plays "too fast" - a 4 minute .ogg goes through in about 3:40, sounding a bit
> high-pitched in the process.

> Any ideas?

Hrmmm. Are you seeing something like:

Loosing too many ticks!
TSC cannot be used as a timesource. (Are you running with SpeedStep?)
Falling back to a sane timesource.

in your dmesg?

I just realized that in clock_fallback() from my lost-tick-speedstep-fix
we don't re-calibrate loops_per_jiffies. The conversion from cycles to
loops should be pretty close, but that might need some additional work. 

Hrmmm..
-john




  parent reply	other threads:[~2003-07-01  0:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28 21:31 2.5.73-mm2 - odd audio problem, bad intel8x0/ac97 clocking Valdis.Kletnieks
2003-06-29  0:10 ` Andrew Morton
2003-06-29 18:10   ` Valdis.Kletnieks
2003-06-29 20:33     ` Alan Cox
2003-06-29 20:56       ` Valdis.Kletnieks
2003-07-01  0:25 ` john stultz [this message]
2003-07-01  0:41   ` Valdis.Kletnieks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1057019147.28319.367.camel@w-jstultz2.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).