Re: iwlagn: "Intel Centrino Advanced-N 6205 AGN" and "AVM Fritz!Box (7390)" incompatible

["Guy, Wey-Yi" <wey-yi.w.guy@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1977 bytes --]

Hi HEnrik,


On Mon, 2011-09-26 at 08:20 -0700, Henrik Friedrichsen wrote:
> Hey Wey,
> 
> Sure! Here's the information you asked for:
> 
> On Mon, Sep 26, 2011 at 4:54 PM, wwguy <wey-yi.w.guy@intel.com> wrote:
> > Hi Henrik,
> >
> > On Mon, 2011-09-26 at 07:07 -0700, Henrik Friedrichsen wrote:
> >> One more thing I have noticed:
> >>
> >> This message is only being printed when I connect to the AP, that I
> >> have problems with:
> >>
> >> Sep 26 07:05:03 dharma kernel: [ 2213.379252] iwlagn 0000:03:00.0: Tx
> >> aggregation enabled on ra = xx:xx:xx:xx:xx:xx tid = 0
> >>
> > this message telling us "11n/aggregation" is started; so looks like the
> > problem is aggregation related.
> I see. Well only after that has been printed, I can surf the internet.
> It takes a few seconds for that message to appear (after DHCP info
> retrieval).
> >
> >> On the APs that work fine, it DOES NOT get printed.
> >
> > I don't see anything special in the dmesg log you send, could you
> > provide us more information?
> >
> > 1. AP brand and model
> AVM Fritz!Box Fon WLAN 7390
> > 2. channel band and number
> It happens in the 2,4GHz and 5GHz frequencies, no matter what channel I use.
> > 3. firmware version
> 17.168.5.3 build 42301
> > 4. system setup (bluetooth or any other wireless devices on the system?)
> It's a Lenovo x220i laptop. It does have a Bluetooth chip, which is,
> however, deactived. Other than that there are no other wireless
> devices.
> > 5. if you can provide us more detail log, it will be great. (loading the
> > iwlagn with debug=0x43fff)
> Here's a more detailed log connecting to that AP in the 5GHz range:
> http://diff.cc/tmp/kernel_iwlagn.log
> >
> >
> > 
not seeing anything stand-out in the log.

few things I will suggest and please give a try:
1. Please try to apply the following two patches I attach here.
2. load the iwlagn with debug=0x45800006, the log will be big, but it
will contain more information on the tx/rx path.

thanks
Wey


[-- Attachment #2: [Internal-wifi-devel]_[PATCH]_iwlagn:_set_the_sequence_control_from_the_transport_layer --]
[-- Type: application/mbox, Size: 5828 bytes --]

[-- Attachment #3: [Internal-wifi-devel]_[PATCH]_iwlagn:_update_rate_scaling_with_BA_notifications --]
[-- Type: application/mbox, Size: 5406 bytes --]