At Thu, 23 Jan 2003 01:35:53 +0100, Tais M. Hansen <[EMAIL PROTECTED]> wrote: > > On Wednesday 22 January 2003 17:23, Takashi Iwai wrote: > > could you test the following two patches? > > with the first one, the driver will calculate the current pointer like > > VIA686 does. if this is ok, no messages will appear. > > The first patch makes artsd freeze the computer for about 10-20 seconds and > then aborts with a "cpu overload" message. ogg123 sometimes plays noise when > starting while speeding through the ogg-file, sometimes it plays normally. > Only ogg123 generated output in syslog which I've attached in > alsa-ogg123-syslog-p1.txt.gz. ok, that's not good...
> > > the second one is to force to increase the index. you'll see debug > > messages, anyway, if POINTER_DEBUG is defined. > > First, removing first patch and applying the second patch. Ogg123 freezes when > started with no sound and a lot of errors. Ctrl-C is caught after about 10 > secs. Syslog output is attached in alsa-ogg123-syslog-p2.txt.gz. Artsd starts > but keep looping a short random piece of noise. No sound can be played/heard > when played. Killing artsd produces the output attached in > alsa-artsd-syslog-p2.txt.gz. hmm... > Applying both patches. Ogg123 and artsd behaves like when only the first patch > was applied. I let ogg123 run a little longer and noticed that sometimes > about half a second noise where played. Syslog errors from using ogg123 this > time is attached in alsa-ogg123-syslog-p1+p2.txt.gz. ah, applying both has no effect.. > Note: POINTER_DEBUG was defined and the initial patch you sent was applied > throughout the test. ok, the attached is the third trial. please appply it solely without the preivous patches. hope this works better... ciao, Takashi
via-pointer-test3.dif
Description: Binary data
