From: Andrew Morton <akpm@digeo.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.73-mm2 - odd audio problem, bad intel8x0/ac97 clocking.
Date: Sat, 28 Jun 2003 17:10:36 -0700 [thread overview]
Message-ID: <20030628171036.4af51e08.akpm@digeo.com> (raw)
In-Reply-To: <200306282131.h5SLVjGk001833@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>
> 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.
>
> lspci -v:
> 00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio (rev 02)
> Subsystem: Cirrus Logic: Unknown device 5959
> Flags: bus master, medium devsel, latency 0, IRQ 11
> I/O ports at d800 [size=256]
> I/O ports at dc80 [size=64]
>
> relevant dmesg output:
> Advanced Linux Sound Architecture Driver Version 0.9.4 (Mon Jun 09 12:01:18 2003 UTC).
> request_module: failed /sbin/modprobe -- snd-card-0. error = -16
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> intel8x0: clocking to 51084
> ALSA sound/pci/intel8x0.c:2520: joystick(s) found
> ALSA device list:
> #0: Intel 82801CA-ICH3 at 0xd800, irq 11
>
> The 'clocking to 51084' is *VERY* suspicious
It could be that do_gettimeofday() has gone silly. Could you
add this patch and see what it says?
sound/pci/intel8x0.c | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
diff -puN sound/pci/intel8x0.c~intel8x0-cleanup sound/pci/intel8x0.c
--- 25/sound/pci/intel8x0.c~intel8x0-cleanup 2003-06-28 17:07:43.000000000 -0700
+++ 25-akpm/sound/pci/intel8x0.c 2003-06-28 17:09:07.000000000 -0700
@@ -2062,10 +2062,8 @@ static void __devinit intel8x0_measure_a
t = stop_time.tv_sec - start_time.tv_sec;
t *= 1000000;
- if (stop_time.tv_usec < start_time.tv_usec)
- t -= start_time.tv_usec - stop_time.tv_usec;
- else
- t += stop_time.tv_usec - start_time.tv_usec;
+ t += stop_time.tv_usec - start_time.tv_usec;
+ printk(KERN_INFO "%s: measured %lu usecs\n", __FUNCTION__, t);
if (t == 0) {
snd_printk(KERN_ERR "?? calculation error..\n");
return;
_
next prev parent reply other threads:[~2003-06-28 23:56 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 [this message]
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
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=20030628171036.4af51e08.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=Valdis.Kletnieks@vt.edu \
--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).