>> anyway, it'd be helpful for debugging if someone can reproduce this >> certainly under a fixed condition... > >Well, about 3 times out of 7 I get the problem, so it's not hard to >reproduce at all. What I'd have to know is where to place the debugging >printk()'s or something like that :(
just wanted to mention that i mis-remembered the situation under which this used to happen with the rme9652 driver. it was an error in the *driver*, not the application, and it was related to the logic for figuring out the hardware buffer pointer being incorrect. i forget the error, and its probably something a bit different anyway (because of the ASIO-style design of the rme9652), but i just wanted to mention it in case it provides any help. once i fixed the driver to get this right, i could never (and have never) heard the problem again. --p ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
