The same program that causes sb16 to become completely wedged causes milder errors in the cs4239 module. Reference: see thread starting at: http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg05525.html
The program runs for a while (sometimes 8 minutes, sometimes less than one minute) and then gets an i/o error. This differs in at least three ways from the sb16 scenario: -- usually it gets the i/o error without having generated any IOCTL_PREPARE() errors. -- On rare occasions it does generate IOCTL_PREPARE() errors, but they are not fatal. -- The ALSA system does not get totally wedged; restarting the userland application gets us back where we started. However one may conjecture that there are elements in common here. My program is continually doing input and output at the same time (i.e. full duplex) ... and is causing input overruns once every 0.5 seconds. It is perhaps a good diagnostic for detecting drivers that don't quite do enough clean-up after an overrun. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
