2009/9/9 Elimar Riesebieter <riese...@lxtec.de>: > * Bailin Deng [090908 20:25 +0200] >> 2009/9/8 Bailin Deng <den...@gmail.com>: > [...] >> > Sep 8 20:00:53 dbl-pc kernel: [26050.488420] ath5k phy0: noise floor >> > calibration timeout (2412MHz) >> > Sep 8 20:01:06 dbl-pc wpa_supplicant[3165]: CTRL-EVENT-SCAN-RESULTS >> > Sep 8 20:02:07 dbl-pc wpa_supplicant[3165]: CTRL-EVENT-SCAN-RESULTS >> > Sep 8 20:03:07 dbl-pc wpa_supplicant[3165]: CTRL-EVENT-SCAN-RESULTS >> > Sep 8 20:04:07 dbl-pc wpa_supplicant[3165]: CTRL-EVENT-SCAN-RESULTS >> > >> > So I really suspect that the audio lagging and the wireless error >> > messages are somehow connected. Is it possible that the kernel is too >> > busy handling the wireless module, so that for a short time it is >> > unable to process the audio? >> >> Some more information about the wireless network: From the >> NetworkManager applet in Gnome, I can see that there are currently 5 >> wireless networks detected by my system (but I am not connected to any >> of them). Usually when I am having the audio lagging problem, the >> NetworkManager applet shows more than 4 wireless networks signals >> available. Yesterday the audio worked fine, and the NetowrkManager >> applet shown no wireless network. Besides, I note that when there are >> more wireless networks available, the lagging events become more >> frequent. That seems to indicate some connection between the wireless >> network and the audio lagging. > > Are you connected via a wireless Network? It seems to be that your > networkmanager tries to connect by him self to an available network. > I don't know networkmanager, because I usually use software > controlled by myself. I hate software, whic tries to think like me > ;-) But there mustbe an option in networkmanager connect only to the > AP you told him. If you don't use wireless shut networkmanager off. > (the best would be to thrown it away)
No I am not connected via wireless network. I use a local ethernet connection. And I have configured NetworkManager to automatically connect to local ethernet only. And NetworkManager applet will NOT connect to any of those wireless networks, unless you explicitly ask it to do so. It only shows you that these networks are available. And the error logs are actually from the kernel module for wireless card driver. But I have no idea how they influence alsa....... > > Elimar > > > -- > Numeric stability is probably not all that > important when you're guessing;-) > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
