There's a lot of noise on this bug, but it's definitely a kernel issue.
I see this quite frequently on Jaunty (amd64) with kernel 2.6.28-8.24.
For instance:
[19298.596118] iwl3945: Error sending REPLY_SCAN_CMD: time out after 500ms.
[19298.596145] iwl3945: No space for Tx
[19298.596150] iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed:
-28
[19298.596155] iwl3945: Error setting new configuration (-28).
[19298.596163] iwl3945: No space for Tx
[19298.596167] iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD:
iwl3945_enqueue_hcmd failed: -28
[19303.597739] iwl3945: No space for Tx
[19303.597748] iwl3945: Error sending REPLY_SCAN_CMD: iwl3945_enqueue_hcmd
failed: -28
[19303.597770] iwl3945: No space for Tx
[19303.597774] iwl3945: Error sending REPLY_RXON: iwl3945_enqueue_hcmd failed:
-28
[19303.597779] iwl3945: Error setting new configuration (-28).
[19303.597786] iwl3945: No space for Tx
Etc etc etc. It goes on like that forever if you don't remove the
kernel module. Removing and reinserting the kernel module makes it
stop. Needless to say, the network doesn't work during these episodes.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
iwl3945: no space for tx, Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd
failed: -28
https://bugs.launchpad.net/bugs/317728
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
