From: "Tais M. Hansen" <tais.hansen@osd.dk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: VIA823x testing
Date: Wed, 29 Jan 2003 00:19:47 +0100 [thread overview]
Message-ID: <200301290019.55309.tais.hansen@osd.dk> (raw)
In-Reply-To: <s5hznplkzyh.wl@alsa2.suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 28 January 2003 17:21, Takashi Iwai wrote:
> > > please check the mixer configuration.
> > > there must be any sounds, even though pops/clicks and error messages
> > > might come.
> > No sound at all. I've tried turning everything up to full volume,
> > unmuting everything, tried all three onboard minijacks. Not a peep.
> hmm, then it seems something goes wrong completely.
> at least, i see the "invalid CURR_PTR" error at each call.
> it's weird. did you see this in the log of ogg123?
Yes. Lots of those. I also noticed something else. Seems like there's some
kind of overflow in the logging or something. I found a few lines that has
been truncated like these:
Jan 28 17:30:44 proficio kernel: ALSA ../alsa-kernel/pci/via82xx.c:733:
invURR_COUNT reg
Jan 28 17:30:46 proficio kernel: ALSA ../alsa-kernel/pcURR_COUNT reg
Jan 28 17:30:46 proficio kernel: ALSA ../alsa-kernel/p3: invalid CURR_COUNT
reg
I'm guessing that too much output comes too fast, filling some buffer and
truncating the rest. It's probably syslogd which truncates, but I thought I'd
mention it anyway.
> > - From what I can see when playing with ogg123, it's speeding through the
> > ogg-file. It took 4.8s to play 10s ogg-file.
> interesting.
> the new patch will put the timestamp at each interrupt, so you can
> measure the period time between interrupts.
> this shoud be (period-size-in-frames * 4 / sample-rate)
I edited the patch. You inited a timeval tval, but referred to tv->sec and
tv->usec. I'm guessing it should have been tval.tv_sec and tval.tv_usec.
> please compare the measured values.
I'm not sure what you mean with 'period-size-in-frames', so I just wrote up
the numbers here.
8 'period elapsed' from ogg123 test (44100 Hz, 2 ch):
1043795039.736837 idx 0 ptr 0x0
+0.008531 idx+1 ptr+0x1000
1043795039.745368 idx 1 ptr 0x1000
+0.001152 idx+1 ptr+0x1000
1043795039.746520 idx 2 ptr 0x2000
+0.012034 idx+1 ptr+0x1000
1043795039.758554 idx 3 ptr 0x3000
+0.012041 idx+1 ptr+0x1000
1043795039.770595 idx 4 ptr 0x4000
+0.004189 idx+1 ptr+0x1000
1043795039.774784 idx 5 ptr 0x5000
+0.000696 idx+1 ptr+0x1000
1043795039.775480 idx 6 ptr 0x6000
+0.012130 idx+1 ptr+0x1000
1043795039.787610 idx 7 ptr 0x7000
5 'period elapsed' from aplay test (44100 Hz, 2 ch, Signed 16 bit Little
Endian) period_size 4410:
1043794327.002204 idx 0 ptr 0x0
+0.012029 idx+5 ptr+0x44e8
1043794327.014233 idx 5 ptr 0x44e8
+0.012031 idx+5 ptr+0x44e8
1043794327.026264 idx 10 ptr 0x89d0
+0.012029 idx+5 ptr+0x44e8
1043794327.038293 idx 15 ptr 0xceb8
+0.012032 idx+6 ptr+0x44e8
1043794327.050325 idx 21 ptr 0x113a0
I'm not sure what to make of this. Sorry.
- --
Regards,
Tais M. Hansen
OSD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iQIVAwUBPjcQGIIvLOJqwYc4AQIWzhAAgk2e6Bpelgc539+zXr3tQhOH6DSPlcQ7
c2J1ta1PkKuqY9OH1uvYqxcIbR2wqQ5wdB6y6zaLsD0pdODQr0adtuY4FX+FiiyB
iMpI23E0T8JY21gw09dmn0hrvfFH/0xsW+rFBtIur+1uHYg/eKLdKs6rHo6vng5h
0NgAbiN2Xd9Mx9yZBVTj81VwZm/d7GRFu52xgafhgtRACcLM4bDve4ErouvhleY4
YClGXcZyBhprYMXxKr0Rv/3lSM+iP2bDis/B1lVotVABQRrino5NbM4CCBr7Hrrt
Zl/Ay1tphQ9sBuqrSumvMJ7IA9FMnt/BjAxuN+7VIQjDSGguYde1oWuinYPXTo//
4BoKRu46/5WOuJzi13aJXAI3pa2V+DVEVPOvmHoodTc8UV2mOWlAsVaUjw7I+ipy
e0R2JvDfL4O2F8XDVUsxjwxwkKlm+70CyM4PtNw1kBrkgDONQ6G9HQkIOe/ie4oh
dQR2btvxv273gsrRdz0JSfYDvd8r3uWjPffNsSzxlQk9q9yORgd2KytBkUZvj5bS
WHPC8R9KAjiAnju9cv+yX9n507VsyEAX594ISLK179bADdzrpZActJRIkvNvYSBh
8CXU4ZkQRPFOrGk5AF0MhGuiWHazOOshX7clxTTl9Tlf1iOEODz3nosJbpEre9aJ
pKqcrOVNBSs=
=6lBB
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-28 23:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200301221234.33054.tais.hansen@osd.dk>
[not found] ` <200301221543.52285.tais.hansen@osd.dk>
[not found] ` <s5hznpt1bn2.wl@alsa2.suse.de>
[not found] ` <200301221647.05780.tais.hansen@osd.dk>
2003-01-22 16:23 ` [Alsa-user] Upgrade problems -addendum Takashi Iwai
2003-01-23 0:35 ` Tais M. Hansen
2003-01-23 10:03 ` Takashi Iwai
2003-01-23 11:15 ` Tais M. Hansen
2003-01-23 11:46 ` Takashi Iwai
2003-01-23 12:36 ` Tais M. Hansen
2003-01-23 15:08 ` Takashi Iwai
2003-01-23 17:50 ` Tais M. Hansen
2003-01-23 18:07 ` Takashi Iwai
2003-01-23 18:43 ` Tais M. Hansen
2003-01-24 9:12 ` Takashi Iwai
2003-01-24 12:41 ` Tais M. Hansen
2003-01-24 13:30 ` Takashi Iwai
2003-01-24 14:12 ` Tais M. Hansen
2003-01-24 15:45 ` Takashi Iwai
2003-01-24 16:40 ` Tais M. Hansen
2003-01-24 17:08 ` Takashi Iwai
2003-01-24 21:24 ` Tais M. Hansen
2003-01-27 10:42 ` Takashi Iwai
2003-01-27 14:42 ` Tais M. Hansen
2003-01-27 15:15 ` Takashi Iwai
2003-01-27 17:01 ` Tais M. Hansen
2003-01-27 17:27 ` Takashi Iwai
2003-01-28 0:43 ` VIA823x testing Tais M. Hansen
2003-01-28 9:31 ` Takashi Iwai
2003-01-28 13:25 ` Tais M. Hansen
2003-01-28 16:21 ` Takashi Iwai
2003-01-28 23:19 ` Tais M. Hansen [this message]
2003-01-24 16:42 ` Re: [Alsa-user] Upgrade problems -addendum Tais M. Hansen
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=200301290019.55309.tais.hansen@osd.dk \
--to=tais.hansen@osd.dk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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