View Single Post
Old 07-13-2012, 07:11 PM   #169
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Terrifying latency. Something must be up. There's a big LOUD surge, then it remembers to turn down, that's a bit odd also...

Something must be up. Even at it's maximum period size of 4096 it's struggling to initialise Full duplex in one swallow. I suspect this may be the kernel glitch I was spouting about. would love to pull some decent errors from somewhere.

All stracing gives me is:

ioctl(5, SNDRV_PCM_IOCTL_READI_FRAMES, 0xbe9559b0) = -1 EAGAIN (Resource temporarily unavailable)
repeated a lot... Then:
octl(5, SNDRV_PCM_IOCTL_READI_FRAMES, 0xbe9559b0) = -1 EPIPE (Broken pipe)

Which is pretty much what I observed before when trying to full duplex the card.

Something must be up. Did I say that already?

Meh. Ill abandon full duplex for the day in favour of tea and twiddling freqs toward the GM++ Viddy viewer. much more fun.
twobob is offline   Reply With Quote