[Bug 308053] Re: iwlagn: cannot allocate SKB buffers
** Changed in: linux-backports-modules-2.6.27 (Ubuntu) Status: New = Invalid -- iwlagn: cannot allocate SKB buffers https://bugs.launchpad.net/bugs/308053 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
[Bug 308053] Re: iwlagn: cannot allocate SKB buffers
Please disregard my posts. My problems extended to Windows XP and Vista. The chip has been replaced with an identical version, and my problem has been resolved. -- iwlagn: cannot allocate SKB buffers https://bugs.launchpad.net/bugs/308053 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
[Bug 308053] Re: iwlagn: cannot allocate SKB buffers
I've been having problems with the iwlagn module. I'm actually using Hardy 8.04.1, and I presume an update that was committed to Intrepid has been sent to Hardy as well. The LiveCD had no problems, and my disk install of Hardy had worked flawlessly for a long time. It is only recently that this has occurred, and it seems related to this thread: http://ubuntuforums.org/showthread.php?t=962070 There is a workaround that was suggested for Intrepid that the users in that thread were unable to use successfully due to the fact that the iwl4965 module was removed from Intrepid in favor of iwlagn. Being on Hardy, I still have the iwl4965 module, so issuing the command to unload iwlagn and iwl4965 then re-load iwl4965 has so far resolved my issues: sudo modprobe -r iwlagn iwl4965 ; sudo modprobe iwl4965 Without the proper module, this command does not function properly. If Intrepid (and presumably Jaunty) were to include iwl4965, then this workaround could be applied. -- iwlagn: cannot allocate SKB buffers https://bugs.launchpad.net/bugs/308053 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
[Bug 308053] Re: iwlagn: cannot allocate SKB buffers
The relevant dmesg output I get when this occurs is as follows: [ 3603.194199] wlan0: No ProbeResp from current AP 00:0f:34:8f:98:d5 - assume out of range [ 3603.939973] wlan0: No STA entry for own AP 00:0f:34:8f:98:d5 [ 3606.456102] wlan0: No STA entry for own AP 00:0f:34:8f:98:d5 [ 3609.478726] wlan0: No STA entry for own AP 00:0f:34:8f:98:d5 [ 3616.213511] wlan0: Initial auth_alg=0 [ 3616.213531] wlan0: authenticate with AP 00:0f:34:8f:98:d5 [ 3616.290410] wlan0: authenticate with AP 00:0f:34:8f:98:d5 [ 3616.446937] wlan0: authenticate with AP 00:0f:34:8f:98:d5 [ 3616.607757] wlan0: authentication with AP 00:0f:34:8f:98:d5 timed out I'm not entirely certain if this is due to SKB buffers, but this occurs on a fairly regular basis. Running the workaround above allows the adapter to reconnect, but I cannot stay connected long enough to transfer a full CD image. -- iwlagn: cannot allocate SKB buffers https://bugs.launchpad.net/bugs/308053 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
[Bug 308053] Re: iwlagn: cannot allocate SKB buffers
Managed to get more syslog output on the bug: [ 2876.725114] iwlagn: Microcode SW error detected. Restarting 0x200. [ 2876.941557] Registered led device: iwl-phy0:radio [ 2876.941877] Registered led device: iwl-phy0:assoc [ 2876.942152] Registered led device: iwl-phy0:RX [ 2876.942422] Registered led device: iwl-phy0:TX It seems to me that the reset should be done on the active connection as well -- maybe NM should catch the microcode exception. -- iwlagn: cannot allocate SKB buffers https://bugs.launchpad.net/bugs/308053 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
