Bug 17592 - iwlagn microcode error when connecting to 11N network
Summary: iwlagn microcode error when connecting to 11N network
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-02 05:39 UTC by rocko
Modified: 2011-01-21 18:26 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.36-rc3
Subsystem:
Regression: No
Bisected commit-id:


Attachments
syslog showing the microcode error (network was unreachable afterwards) (18.66 KB, text/plain)
2010-09-02 05:39 UTC, rocko
Details
syslog showing the microcode error (but network worked afterwards) (23.50 KB, text/plain)
2010-09-02 05:53 UTC, rocko
Details

Description rocko 2010-09-02 05:39:31 UTC
Created attachment 28792 [details]
syslog showing the microcode error (network was unreachable afterwards)

When connecting to an 11N network using kernel 2.6.36-rc3 I always get a microcode error after a DHCP address is obtained, which makes it look to Network Manager like the card is connected, but I can't ping the access point (network unreachable).

The hardware is: 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 02).

The firmware version that iwlagn reports it is loading is 228.61.2.24. This is the same firmware that gets loaded from the 2.6.35.4 kernel. The microcode error is reported in the 2.6.35.4 kernel as well, but for some reason that kernel usually recovers from the error.

On one occasion I managed to get 2.6.36-rc3 to connect successfully (after multiple modprobe -r iwlagn && modprobe iwlagn commands). The microcode error occurred in this case, but the connection was working afterwards. It lost the connection an hour or so later when the microcode error occurred again.

Disabling 11N (with "options iwlagn 11n_disable=1" in /etc/modprobe.d/iwlang.conf) doesn't help; nor does a complete system reboot.

The driver doesn't have any problems with my home 11g network.
Comment 1 rocko 2010-09-02 05:53:45 UTC
Created attachment 28802 [details]
syslog showing the microcode error (but network worked afterwards)

This is the syslog from when I managed to connect successfully to the network. It looks pretty similar to the failed connection logs, though.
Comment 2 rocko 2010-10-12 03:38:33 UTC
It's still a problem in 2.6.36-rc7 (a major one for me on this router because the error almost invariably kills the network connection in 2.6.36).
Comment 3 wey-yi.w.guy 2010-10-15 14:18:12 UTC
It is Intel 3965 device, correct?
Could you load the module with debug flag = 0x43fff which can give us more info.
#modprobe iwlagn debug=0x43fff

Thanks
Wey
Comment 4 rocko 2010-10-26 05:28:57 UTC
I haven't had a chance to try that 11N network recently, but I'll run the debug next time I'm out there.
Comment 5 John W. Linville 2011-01-21 18:26:14 UTC
Closing due to lack of information requested in comment 3...

Note You need to log in before you can comment on or make changes to this bug.