[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#677880: iwlwifi: flakey and slow connection, high "invalid misc" count (Re: Same problem here.)



notfound 677880 3.2.12-1
found 677880 linux-2.6/3.2.16-1
retitle 677880 iwlwifi: flakey and slow connection, high "invalid misc" count
quit

Hi,

Olivier Berger wrote:

> I think you didn't experience exactly the same problem explained in the
> original report. My wifi wasn't disconnecting, but I was just annoyed by the
> syslog pollution linked to cfg80211.
>
> So cloning to another bug report hoping you don't mind.

Victor, your bug is now #677880.

Victor Pablos Ceruelo wrote:

> When it does not connect it is usual to see in the logs
[...]
> wlan0: authenticated
> wlan0: associate with 88:25:2c:92:3d:aa (try 1)
> wlan0: RX AssocResp from 88:25:2c:92:3d:aa (capab=0x421 status=0 aid=1)
> wlan0: associated
[...]
> but it seems to be that dhcp does not receive any package.
> using static ip does not fix this, nor using a different dhcp client
> (I've tried pump and dhclient, now I'm using dhcpcd)
>
> I think the problem is related to the "Invalid misc" field.
> Now it's 384, but it is usually over 10.000
> (although I have not seen 40.000, it disconnects before always).

Interesting.

[...]
> Same problem with zd1211rw (this time it is even worst, it says it's
> connected but it is not).

Ok, so either both drivers have a similar bug (or common code they
both call is broken) or there is something in the environment that is
responsible for both sets of symptoms.  Either seems possible.

[...]
> This is reportbug info from the other machine.
[...]
> It switches between 11Mb/s and 1Mb/s very often,
> as the other machine.

Now I'm getting lost.  Can you please summarize:

 - what the setup is like --- what are the relevant machines, what
   kind of wireless router, etc

 - what kind of card each machine uses

 - what kernels you have tried on each machine and what happened with
   each

Then for concreteness, let's focus on getting this fixed on a single
machine and card (e.g., the first with the iwlwifi adapter) and go
from there.

Hope that helps,
Jonathan



Reply to: