On Thu, Jan 16, 2014 at 12:25:42AM -0500, Olivier Langlois wrote: > On 01/15/2014 12:01 PM, Larry Finger wrote: > >On 01/15/2014 12:37 AM, Olivier Langlois wrote: > >>How to reproduce: > >> > >>1. Enable Wifi while not connecting to any AP. > >>2. lano1106@hpmini ~/Music $ aplay -c1 sine.wav > >>underrun!!! (at least 1856093977.967 ms long) Indeed, that timing is fishy. I've looked at the alsa-devel thread [1] and your problem description there. At OLPC during development we found similar symptoms showing up in ALSA playback that were contributed to other drivers, but the underlying causes were in the ALSA driver for our codec chip, and the other drivers were changing the appearance of the fault only because of timing changes. But there's no need to conclude that interrupts were disabled or delayed. There can be many other causes. The timing miscalculation by ALSA might be important. I can't figure out how a wireless driver can easily cause that. 1. http://mailman.alsa-project.org/pipermail/alsa-devel/2014-January/071142.html -- James Cameron http://quozl.linux.org.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
