Bug 15891 - Intel WiFi Link 5150ABG - connection broken or freezing when transferring large files
Summary: Intel WiFi Link 5150ABG - connection broken or freezing when transferring lar...
Status: CLOSED CODE_FIX
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-05-01 13:00 UTC by RussianNeuroMancer
Modified: 2010-06-14 22:16 UTC (History)
3 users (show)

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


Attachments
patch on top of 2.6.32.15 (8.15 KB, patch)
2010-06-02 21:59 UTC, Shanyu Zhao
Details | Diff

Description RussianNeuroMancer 2010-05-01 13:00:05 UTC
When I transfer large files (few Gb for example) wifi connection can be broken or freezing. If this happened - I can't connect to AP until reboot the system.

What additional information would need to provide?
Comment 1 Shanyu Zhao 2010-05-03 22:09:20 UTC
Hi,

This probably is a duplicate of another bug that we've already known.
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2037

The fix for that problem is not in 2.6.32. I noticed that you also tried 2.6.34rc5. Did you see the same problem with that kernel? If you still see this problem, please compile the driver with debug info, load driver with option "debug=0x43fff" and send us debug logs while reproducing this problem.

Thanks,
Shanyu
Comment 2 RussianNeuroMancer 2010-05-24 12:41:41 UTC
This issue not reproduced with 802.11g connections, only with 802.11n. But by another bug I can't connect in 802.11n-mode with latest version of driver, and can't provide debug info until this bug https://bugzilla.kernel.org/show_bug.cgi?id=15892 is fixed.
Comment 3 Shanyu Zhao 2010-05-26 19:17:27 UTC
This is a bug for 2.6.32 stable kernel. The kernel incorrectly recognize all 5150 devices to be AGN but actually the user has an ABG device. Please refer to the other bug for detail:
https://bugzilla.kernel.org/show_bug.cgi?id=15892

Shanyu
Comment 4 John W. Linville 2010-05-26 19:19:47 UTC
Can you identify which patch corrects the identification of this device?
Comment 5 RussianNeuroMancer 2010-05-26 19:30:47 UTC
I tried, but no success.
Comment 6 Reinette Chatre 2010-06-02 17:19:33 UTC
The patch is:

commit 7a034ec5ece275f12826fda1e9f6cbd29165baef
Author: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Date:   Fri Nov 13 12:03:31 2009 -0800

    iwlwifi: update supported PCI_ID list for 5xx0 series
    
    Update the PCI_ID list for 5xx0 series.
    Remove all the PCI_IDs which never made into production or not longer in
    production.
    
    Also make sure the supported bands(a/b/g/n) match specified PCI_IDs
    
    Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
    Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>


It does not apply to 2.6.32. Since 2.6.34 does not have the identification issue, can you try that kernel to see if you are still running into this broken connection issue?
Comment 7 Shanyu Zhao 2010-06-02 21:59:05 UTC
Created attachment 26628 [details]
patch on top of 2.6.32.15

I back-ported the patch Reneitte pointed out. It should cleanly apply to 2.6.32.15. Can you please give it a try to see if your device is correctly recognised as ABG instead of AGN?
Comment 8 RussianNeuroMancer 2010-06-07 08:10:08 UTC
> Can you please give it a try to see if your device is correctly
recognised as ABG instead of AGN?
Yes, device correctly recognised.

> Since 2.6.34 does not have the identification issue, can you try that kernel
> to see if you are still running into this broken connection issue?
I check this bug with 2.6.35rc1 kernel. It's looks like in g-mode this issue not present. Because now device recognized like ABG instead of AGN, n-mode not available. In g-mode I can't reproduce connection freezing when transferring large files.

I think this bug can be closed.
Comment 9 Shanyu Zhao 2010-06-14 22:16:42 UTC
The patch has been submitted to 2.6.32 stable kernel.

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