RT2561 connection loss, cannot reconnect

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=5387

c666

25-05-2009 10:06:59

Hey,

for a long time everything worked fine, but since yesterday I encounter some strange behaviour

While the card manages to connect at boot time it loses the connection after a while and does not
manage to reconnect. I don't have a clue what's going wrong.

The lspci output
[code1hkk59v9]
05:00.0 Network controller: RaLink RT2561/RT61 802.11g PCI (rev ff)[/code1hkk59v9]

And dmesg at boot

[code1hkk59v9]
[ 31.804958] firmware: requesting rt2561s.bin
[ 34.087740] wlan0: Initial auth_alg=0
[ 34.087744] wlan0: authenticate with AP 00:1f:3f:d7:02:1b
[ 34.098737] wlan0: RX authentication from 00:1f:3f:d7:02:1b (alg=0 transaction=2 status=0)
[ 34.098740] wlan0: authenticated
[ 34.098743] wlan0: associate with AP 00:1f:3f:d7:02:1b
[ 34.103293] wlan0: RX AssocResp from 00:1f:3f:d7:02:1b (capab=0x431 status=0 aid=1)
[ 34.103293] wlan0: associated
[ 34.103293] wlan0: switched to short barker preamble (BSSID=00:1f:3f:d7:02:1b)
[ 34.103293] wlan0 (WE) : Wireless Event too big (366)
[ 44.410449] NET: Registered protocol family 10
[/code1hkk59v9]

and when it loses the connection

[code1hkk59v9]
[ 1855.129537] ACPI: PCI Interrupt 0000:01:00.1[B] -> GSI 17 (level, low) -> IRQ 17
[ 1855.129555] PCI: Setting latency timer of device 0000:01:00.1 to 64
[ 2340.507438] skge 0000:05:02.0: PCI error cmd=0x17 status=0x82b0
[ 2340.507544] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.508935] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.507438] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.508935] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.507438] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.511435] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.529279] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.529279] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.529279] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.529279] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.529279] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.532492] skge 0000:05:02.0: PCI error cmd=0x157 status=0xc2b0
[ 2340.532492] skge 0000:05:02.0: unable to clear error (so ignoring them)
[ 2347.249974] wlan0: No ProbeResp from current AP 00:1f:3f:d7:02:1b - assume out of range
[ 2348.384004] wlan0: Initial auth_alg=0
[ 2348.384009] wlan0: authenticate with AP 00:1f:3f:d7:02:1b
[ 2348.617402] wlan0: authenticate with AP 00:1f:3f:d7:02:1b
[ 2348.838142] wlan0: authenticate with AP 00:1f:3f:d7:02:1b
[ 2349.039027] wlan0: authentication with AP 00:1f:3f:d7:02:1b timed out
[ 2812.092047] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[/code1hkk59v9]

That does not look good, does it? Are there any other logs that might help?
I appreciate any suggestions/help!

P.S. Attached are the whole outputs.

c666

25-05-2009 17:11:04

Just figured out that there seems to be no coherence between the PCI error and the wifi problem,
because the PCI interrupt occurred again, but the wireless still works.
Also the wireless worked fine today. Maybe it was just some strange random thing.

Still the PCI stuff worries me, but I guess here is not the right place to discuss that.

Hilariousity

21-06-2009 17:11:29

I've had that happen to me a couple of times. I would walk away from my laptop for a while and when I came back the link light for the card would no longer be turned on and I would not be able to bring up the card with ifconfig wlan0 up. I have a hypothesis that if you run an application that constantly needs an internet connection like an instant messenger your're OS will not be able to turn off the chipset because it is in use. But I'm a noob and am just taking a guess mrgreen

pdxrlk

07-08-2009 14:19:55

I have a similar problem - and unfortunately it happens on my machine running DHCPD and DNS -( so everything else in the house loses its connection whenever this occurs. I hear about it immediately too!

When this occurs I cannot ping the server via DNS name nor IP address. At the server console I can make the problem go away by pinging the gateway/router (192.168.1.1) or any other machine on the network except the server itself. All gets happy again. It's as if pinging outside of the localhsot reasserts the link to the wireless hub, I don't know... any ideas on how to debug further?