Re: carl9170 disconnects under load

[Pavel Machek]

Hi!

> > I'm testing driver from -wireless testing, cca 2.6.26-rc7.
> > 
> > It seems to work (up to 802.11n speeds -- I've seen iwconfig claiming
> > 121 MB/sec), but disconnects rather quickly when under load:
> > 
> > telnet 192.168.1.3 chargen > /dev/null
> > 
> > The machine is powerpc mpc5200b board, with OHCI driver -- it is not
> > capable of USB2.0 speeds.
> 
> So I tried with different AP, one not capable of 802.11n speeds. It
> fails in different way :-(. But this one is with my backport to
> 2.6.34...

But it fails with wireless-testing tree, too :-(.

Linux mpc5200b 2.6.36-rc8-wl-pma-48197-gdcae733-dirty #43 Tue Oct 26
 12:06:21 CEST 2010 ppc

								Pavel

PHY: f0003000:00 - Link is Up - 100/Full
warning: `named' uses 32-bit capabilities (legacy support in use)
process `named' is using obsolete setsockopt SO_BSDCOMPAT
ieee80211 phy0: device now idle
ieee80211 phy0: device no longer idle - scanning
wlan0: authenticate with 00:11:95:05:30:d7 (try 1)
wlan0: authenticated
ieee80211 phy0: device now idle
ieee80211 phy0: device no longer idle - working
wlan0: associate with 00:11:95:05:30:d7 (try 1)
wlan0: RX AssocResp from 00:11:95:05:30:d7 (capab=0x421 status=0
aid=1)
wlan0: associated
ieee80211 phy0: Allocated STA 00:11:95:05:30:d7
ieee80211 phy0: Inserted STA 00:11:95:05:30:d7
usb 1-1: restart device (4)
usb 1-1: firmware upload failed (-110).
usb 1-1: Failed to restart device  (-110).
ieee80211 phy0: writing reg 0x1c36f0 (val 0x5000) failed (-5)
wlan0: deauthenticating from 00:11:95:05:30:d7 by local choice
(reason=3)
ieee80211 phy0: Removed STA 00:11:95:05:30:d7
ieee80211 phy0: Destroyed STA 00:11:95:05:30:d7
ieee80211 phy0: device now idle
cfg80211: Calling CRDA to update world regulatory domain
usb 1-1: reset full speed USB device using of:ppc-of-ohci and address
2
-/bin/sh-3.00# usb 1-1: device descriptor read/64, error -110
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/