Hrm. I haven't run into any such issue yet, and I'm going on two days of uptime. That said, I did wind up having a nonrelated issue with the wireless access point here, it apparently does not like running traffic at full capacity on the WLAN and overheated and I had to fall back to using wired while it was unplugged. But once it cooled down and was plugged back in, I was able to get back on again and all was well…
Anything in your dmesg or /var/log/kern.log or /var/log/daemon.log that shows any issues with your WLAN under 2.6.32.3? --- Mike On Wed, Jan 13, 2010 at 8:05 AM, Tyrael <marco.croci...@gmail.com> wrote: > With 2.6.32.3 the situation is better but with problems. > After some hours (8? 10?) I come back to the PC and the connection was lost. > The ping command that pings every 3 seconds my router was giving: > > ping: sendmsg: No buffer space available > ping: sendmsg: No buffer space available > ping: sendmsg: No buffer space available > > Restarting network-manager and umounting/mounting the module doesn't > fix the connection. > > Marco > > On Tue, Jan 12, 2010 at 5:21 PM, Michael B. Trausch <m...@trausch.us> wrote: >> On Tue, Jan 12, 2010 at 6:20 AM, Kunal Gangakhedkar >> <kunal.gangakhed...@gmail.com> wrote: >>> On Monday 11 Jan 2010 9:56:47 pm Michael B. Trausch wrote: >>>> I have 2.6.32.3 installed on Karmic, and my problems with this issue >>>> have gone away. Would it be of any use to try to bisect the kernel to >>>> provide a patch here for Karmic, or is someone already working on such a >>>> thing? (I ask because it is pretty important that I get back to the >>>> Karmic kernel, because VirtualBox in Karmic does not work with 2.6.32.3, >>>> and I use it a good amount.) >>>> >>> >>> Slightly off-topic, but you could simply do "sudo service vboxdrv setup" >>> or "sudo invoke-rc.d vboxdrv setup" to recompile the VBox drivers >>> after updating the kernel. >>> This works unless the kernel API is changed drastically. >>> >>> I use it all the time. >> >> Right, I am aware of how to do that. DKMS is in Ubuntu to make this >> simpler (thanks, Dell!), since DKMS manages the module builds. The >> problem is similar to the NVIDIA module problem back with 2.6.28, >> where the kernel API changed in some way that was never guaranteed to >> be stable in the first place. >> >> I wound up simply updating VBox, but still the core issue here is this: >> >> If I bisect the kernel to attempt to isolate a patch that fixes ath9k >> in Karmic's kernel, will an Ubuntu Kernel Team member take that patch >> and get it into Ubuntu? If that's not a guaranteed "Yes", I am not >> going to try, because I have my system working pretty well for me and >> I am kind of tired of submitting debdiffs and them getting ignored >> half the time. I don't figure that this will be an easy task, but I >> am willing to do it *if* I know for sure that it will be of benefit to >> others. >> >> --- Mike >> >> -- >> ath9k disassociates/reassociates a lot >> https://bugs.launchpad.net/bugs/414560 >> You received this bug notification because you are a direct subscriber >> of the bug. >> > > -- > ath9k disassociates/reassociates a lot > https://bugs.launchpad.net/bugs/414560 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in The Linux Kernel: Fix Released > Status in “linux-backports-modules-2.6.31” package in Ubuntu: Confirmed > > Bug description: > I cannot find any rhyme or reason to this, but my > > 01:00.0 Network controller: Atheros Communications Inc. AR928X Wireless > Network Adapter (PCI-Express) (rev 01) > > seems to like to disassociate/reassociate a lot since I started testing > karmic as of alpha 4. > > A typical dmesg excerpt: > > [ 1881.988111] wlan0: no probe response from AP 00:15:e9:13:47:60 - > disassociating > [ 1883.367859] wlan0: authenticate with AP 00:15:e9:13:47:60 > [ 1883.370161] wlan0: authenticated > [ 1883.370181] wlan0: associate with AP 00:15:e9:13:47:60 > [ 1883.372802] wlan0: RX ReassocResp from 00:15:e9:13:47:60 (capab=0x431 > status=0 aid=1) > [ 1883.372822] wlan0: associated > [ 1892.008117] wlan0: no probe response from AP 00:15:e9:13:47:60 - > disassociating > [ 1893.385338] wlan0: authenticate with AP 00:15:e9:13:47:60 > [ 1893.385521] wlan0: authenticate with AP 00:15:e9:13:47:60 > [ 1893.388175] wlan0: authenticated > [ 1893.388196] wlan0: associate with AP 00:15:e9:13:47:60 > [ 1893.391563] wlan0: RX ReassocResp from 00:15:e9:13:47:60 (capab=0x431 > status=0 aid=1) > [ 1893.391585] wlan0: associated > [ 1926.988135] wlan0: no probe response from AP 00:15:e9:13:47:60 - > disassociating > [ 1928.365306] wlan0: authenticate with AP 00:15:e9:13:47:60 > [ 1928.367426] wlan0: authenticated > [ 1928.367442] wlan0: associate with AP 00:15:e9:13:47:60 > [ 1928.370948] wlan0: RX ReassocResp from 00:15:e9:13:47:60 (capab=0x431 > status=0 aid=1) > [ 1928.370969] wlan0: associated > [ 1966.988114] wlan0: no probe response from AP 00:15:e9:13:47:60 - > disassociating > [ 1968.366568] wlan0: authenticate with AP 00:15:e9:13:47:60 > [ 1968.368624] wlan0: authenticated > [ 1968.368643] wlan0: associate with AP 00:15:e9:13:47:60 > [ 1968.371872] wlan0: RX ReassocResp from 00:15:e9:13:47:60 (capab=0x431 > status=0 aid=1) > [ 1968.371893] wlan0: associated > > Performance drops significantly when this starts going on. At times it > becomes impossible to look up hosts, etc. Other times, it will run fine for > hours on end. > > ProblemType: Bug > AplayDevices: > **** List of PLAYBACK Hardware Devices **** > card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > Architecture: i386 > ArecordDevices: > **** List of CAPTURE Hardware Devices **** > card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: matt 3290 F.... pulseaudio > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: > Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16' > Mixer name : 'Realtek ALC269' > Components : 'HDA:10ec0269,1043834a,00100004' > Controls : 12 > Simple ctrls : 7 > Date: Sun Aug 16 17:15:46 2009 > DistroRelease: Ubuntu 9.10 > MachineType: ASUSTeK Computer INC. 1000HE > Package: linux-image-2.6.31-5-generic 2.6.31-5.24 > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-5-generic > root=UUID=564b6024-8d7a-4d50-8410-563167a8756a ro quiet splash > ProcEnviron: > PATH=(custom, no user) > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-5.24-generic > RelatedPackageVersions: > linux-backports-modules-2.6.31-5-generic N/A > linux-firmware 1.15 > SourcePackage: linux > Tags: ubuntu-unr > Uname: Linux 2.6.31-5-generic i686 > dmi.bios.date: 07/23/2009 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1002 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: 1000HE > dmi.board.vendor: ASUSTeK Computer INC. > dmi.board.version: x.xx > dmi.chassis.asset.tag: 0x00000000 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTek Computer INC. > dmi.chassis.version: x.x > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr1002:bd07/23/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: > dmi.product.name: 1000HE > dmi.product.version: x.x > dmi.sys.vendor: ASUSTeK Computer INC. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/linux/+bug/414560/+subscribe > -- ath9k disassociates/reassociates a lot https://bugs.launchpad.net/bugs/414560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
