Skip to contentSkip to conversation

ipw2200: Driver lockup

DISCUSSION Ralf Baechle 4 participants 4 messages Jul 19, 2006 – Jul 20, 2006

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

I got the driver to die several times under the extreme condition at the KS / OLS with dozens to hundreds of other machines in the same room. The last kernel message I got from about the time when wireless died was

eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full.

Ralf

#1 lore raw
Quoted 5 lines · Ralf Baechle

I got the driver to die several times under the extreme condition at the KS / OLS with dozens to hundreds of other machines in the same room. The last kernel message I got from about the time when wireless died was

eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full.

I actually get this quite a bit too, at least a couple times per day. Sometimes the device goes down and you have to rmmod ipw2200, other times it recovers. But quite annoying anyway.

Anyone know exactly what that message means, and possibly how to fix it?

Dan

Quoted 5 lines

Ralf
-
To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw
Quoted 5 lines · Dan Williams
Quoted 4 lines · Ralf Baechle

I got the driver to die several times under the extreme condition at the KS / OLS with dozens to hundreds of other machines in the same room. The last kernel message I got from about the time when wireless died was

Quoted 7 lines
Quoted 1 line

eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full.

I actually get this quite a bit too, at least a couple times per day. Sometimes the device goes down and you have to rmmod ipw2200, other times it recovers. But quite annoying anyway.

Anyone know exactly what that message means, and possibly how to fix it?

For what it is worth, there was a patch for this posted back in January. It stirred-up a kerfluffle, so it never got merged. FWIW, it touches on 802.11e QoS and multiple TX queues -- my personal favorite wireless subject...NOT!

The thread is available here (first post not connected to follow-up thread for some reason):

	http://marc.theaimsgroup.com/?l=linux-netdev&m=113809246102858&w=2
	http://marc.theaimsgroup.com/?l=linux-netdev&m=113814103024576&w=2

Given that half a year has passed, does anyone have any better ideas now? Should I merge the patch? Or is the cure worse than the disease?

John

Signature · 2 lines
John W. Linville
[email protected]
#3 lore raw
Quoted 5 lines · John W. Linville

For what it is worth, there was a patch for this posted back in January. It stirred-up a kerfluffle, so it never got merged. FWIW, it touches on 802.11e QoS and multiple TX queues -- my personal favorite wireless subject...NOT!

Quoted 8 lines

The thread is available here (first post not connected to follow-up thread for some reason):

	http://marc.theaimsgroup.com/?l=linux-netdev&m=113809246102858&w=2
	http://marc.theaimsgroup.com/?l=linux-netdev&m=113814103024576&w=2

Given that half a year has passed, does anyone have any better ideas now? Should I merge the patch? Or is the cure worse than the disease?

The patch from Stefan Rompf in the second link has already been merged. The first one was already merged (with slightly difference). We can just remove the ieee80211 warning now.

[PATCH] ieee80211: remove ieee80211_tx() is_queue_full warning

---

net/ieee80211/ieee80211_tx.c +0 -7
@@ -533,13 +533,6 @@ int ieee80211_xmit(struct sk_buff *skb, 
 			return 0;
 		}
 
-		if (ret == NETDEV_TX_BUSY) {
-			printk(KERN_ERR "%s: NETDEV_TX_BUSY returned; "
-			       "driver should report queue full via "
-			       "ieee_device->is_queue_full.\n",
-			       ieee->dev->name);
-		}
-
 		ieee80211_txb_free(txb);
 	}