Red Hat Bugzilla – Bug 445201
kernel: iwl4965: Can not allocate SKB buffers
Last modified: 2008-11-24 13:16:09 EST
Description of problem: May 5 09:14:19 nbecker1 kernel: iwl4965: Can not allocate SKB buffers Version-Release number of selected component (if applicable): kernel-2.6.25-14.fc9.x86_64 How reproducible: Don't know Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
May 5 08:53:15 nbecker1 kernel: iwl4965: Error sending REPLY_TX_PWR_TABLE_CMD: Already sending a host command May 5 08:53:15 nbecker1 kernel: iwl4965: Error sending REPLY_RXON: Already sending a host command May 5 08:53:15 nbecker1 kernel: iwl4965: Error setting new configuration (-16). May 5 08:53:15 nbecker1 kernel: iwl4965: Microcode SW error detected. Restarting 0x82000000. May 5 08:53:15 nbecker1 kernel: iwl4965: Error sending REPLY_RXON_TIMING: time out after 500ms. May 5 08:53:15 nbecker1 kernel: iwl4965: REPLY_RXON_TIMING failed - Attempting to continue. May 5 08:53:15 nbecker1 kernel: iwl4965: Error sending REPLY_RXON_ASSOC: time out after 500ms.
Does the message in the original comment occur frequently? Or rarely? It looks like something that might happen occasionally but which should not prevent the driver from working. The messages in comment 1 are something different. Do you see them often? Does the driver continue to work? Or not?
'Already sending' occurs 38 times in last about 24 hours - keep in mind all that time I haven't actually _used_ the wireless connection - it's been connected wired. SKB occurs: 7:May 5 09:14:19 nbecker1 kernel: iwl4965: Can not allocate SKB buffers 8:May 5 09:14:48 nbecker1 kernel: iwl4965: Can not allocate SKB buffers 9:May 5 09:14:49 nbecker1 kernel: iwl4965: Can not allocate SKB buffers 10:May 5 09:15:53 nbecker1 kernel: iwl4965: Can not allocate SKB buffers 11:May 5 09:15:54 nbecker1 kernel: iwl4965: Can not allocate SKB buffers 12:May 5 09:51:21 nbecker1 kernel: iwl4965: Can not allocate SKB buffers
Neal, could you attach the contents of /proc/meminfo when the "Can not allocate SKB buffers" message has recently appeared? It looks like it is a little bursty, which makes some sense to me depending on how memory is being used on your system.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I saw this today (kernel-2.6.24.7-92.fc8): a whole slew of them. Reloaded the iwl4965 module just in case. Came as I was downloading a torrent at about 800KiB/s or so, I'll see if I can reproduce it.
OK, here we go. Torrent coming in at about 200KiB/s, 57 active connections. I've attached a dmesg output from around the event (notice all the unknown symbol messages, must've been when I removed iwl4965) and /proc/meminfo from around that time as well. It *seems* that it's actually provoked by other activity: I was reading an ISO image from a DVD at the time with K3B. I've got the torrent going again at around 380KiB/s. No problems so far. Let's try creating the image again, restart Deluge... OK, just seen a few, but this is probably a coincidence. The error seems to turn up more when the number of connections rises.
Created attachment 305869 [details] dmesg near the SKB allocation failure
Created attachment 305870 [details] /proc/meminfo just after SKB message
John, I don't know if the original reporter still sees this bug, but I'll check the NEEDINFO box below.
Not seeing it in my last 2 /var/log/messages
I'm going to have to ask that this be re-opened, sorry! Just saw: iwlagn: Can not allocate SKB buffers in a dmesg from kernel 2.6.27.6-43.fc9.x86_64.
Nov 19 06:53:33 nbecker1 kernel: Linux version 2.6.27.5-37.fc9.x86_64 (mockbuild@) (gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC) ) #1 SMP Wed Nov 12 18:31:37 EST 2008 ... Nov 19 13:54:02 nbecker1 kernel: iwlagn: Can not allocate SKB buffers
Does the device fail afterwards? Or just that single message in the logs?
They seem to be rather intermittent: [root@rhapsody james]# grep SKB /var/log/messages* /var/log/messages-20081102:Oct 26 13:36:30 rhapsody kernel: iwl4965: Can not allocate SKB buffers /var/log/messages-20081123:Nov 21 04:53:16 rhapsody kernel: iwlagn: Can not allocate SKB buffers /var/log/messages-20081123:Nov 22 22:53:55 rhapsody kernel: iwlagn: Can not allocate SKB buffers The device continues OK, didn't notice anything was amiss until I ran dmesg. I'll try downloading some torrents again, see if I can reproduce the bursts I was seeing earlier.
I don't see any problems with my device (kernel 2.6.27.5-37.fc9.x86_64), just the mesage.
This has also been seen in Ubuntu --- see https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/250139 --- with a bit more detail than we have here. Some of the content of their reports seems familiar to me (message coincident with heavy disc activity, etc.).