Created attachment 111151 [details] full lspci output I have new wireless intel hardware that is incompatible with any kernel older than 3.11. As the connectivity on the 3.11 kernel was very spoty (frequent drops often resulting in me having to reboot in order to get it to work again) I started compiling 3.12rc. with 3.12rc3 the reception apeared to be better but still got drops (drops always recovered - i.e. it reconnected). With 3.12rc4 I have absolutely no issues. I get a decent wifi signal and the connection doesn't drop. With 3.12rc5 the reception (i.e. the number of bars) is better than 3.11 but I'm getting the frequent drops again resulting in me having to reboot (usually back into rc4) OS: Ubuntu 13.10 Laptop: Lenovo Ideapad u430p Hardware: See lspci output below (full output attached) ================================ ~$ sudo lspci -v 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) Subsystem: Lenovo Device 3801 Flags: bus master, fast devsel, latency 0, IRQ 62 I/O ports at 5000 [size=256] Memory at b5504000 (64-bit, non-prefetchable) [size=4K] Memory at b5500000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] #1e Kernel driver in use: r8169 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) Subsystem: Intel Corporation Wireless-N 7260 Flags: bus master, fast devsel, latency 0, IRQ 65 Memory at b5400000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 0c-8b-fd-ff-ff-31-5f-4c Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?> Kernel driver in use: iwlwifi
please add the dmesg output. thanks
Created attachment 111271 [details] latest dmesg output I'm no expert at all on the log files, however, I'm seing far more info on the kernel log and syslog for iwlwifi. SHould I upload those as well?
please do. From what I see it seems you don't even load the right kernel module which is a bug we have seen in other thread on Fedora. With the state I see for the moment, you won't be able to scan even.
Created attachment 111281 [details] syslog compressed syslog
I'm not able to upload the compressed kernel log (it's 1.2mb) I keep getting errors.
thanks - this was helpful. Please send the output of iw reg get and iw phy thanks
Also - I just diffed RC4 and RC5 and they're pretty much the same wrt. wireless / drivers
Just for the record - you have plenty of ASSERT 14FC (info for other Intel WiFi folks who might look at this bug)
~$ iw reg get country 00: (2402 - 2472 @ 40), (3, 20) (2457 - 2482 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS (2474 - 2494 @ 20), (3, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS (5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS (5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS ~$ iw phy Wiphy phy0 Band 1: Capabilities: 0x1062 HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 3839 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 4 usec (0x05) HT TX/RX MCS rate indexes supported: 0-15, 32 Frequencies: * 2412 MHz [1] (16.0 dBm) * 2417 MHz [2] (16.0 dBm) * 2422 MHz [3] (16.0 dBm) * 2427 MHz [4] (16.0 dBm) * 2432 MHz [5] (16.0 dBm) * 2437 MHz [6] (16.0 dBm) * 2442 MHz [7] (16.0 dBm) * 2447 MHz [8] (16.0 dBm) * 2452 MHz [9] (16.0 dBm) * 2457 MHz [10] (16.0 dBm) * 2462 MHz [11] (16.0 dBm) * 2467 MHz [12] (16.0 dBm) (passive scanning, no IBSS) * 2472 MHz [13] (16.0 dBm) (passive scanning, no IBSS) Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps (short preamble supported) * 5.5 Mbps (short preamble supported) * 11.0 Mbps (short preamble supported) * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps max # scan SSIDs: 20 max scan IEs length: 195 bytes Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0 RX 0 Supported interface modes: * managed * AP * AP/VLAN * monitor * P2P-client * P2P-GO * Unknown mode (10) software interface modes (can always be added): * AP/VLAN * monitor valid interface combinations: * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ Unknown mode (10) } <= 1, total <= 3, #channels <= 1 Supported commands: * new_interface * set_interface * new_key * new_beacon * new_station * new_mpath * set_mesh_params * set_bss * authenticate * associate * deauthenticate * disassociate * join_ibss * join_mesh * remain_on_channel * set_tx_bitrate_mask * action * frame_wait_cancel * set_wiphy_netns * set_channel * set_wds_peer * Unknown command (84) * Unknown command (87) * Unknown command (85) * Unknown command (89) * Unknown command (92) * testmode * connect * disconnect Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * Unknown mode (10): 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0x40 0xb0 0xc0 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * mesh point: 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * Unknown mode (10): 0x40 0xd0 Device supports RSN-IBSS. WoWLAN support: * wake up on disconnect * wake up on magic packet * wake up on pattern match, up to 20 patterns of 16-128 bytes * can do GTK rekeying * wake up on GTK rekey failure * wake up on EAP identity request * wake up on 4-way handshake * wake up on rfkill release HT Capability overrides: * MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length * supported channel width * short GI for 40 MHz * max A-MPDU length exponent * min MPDU start spacing Device supports TX status socket option. Device supports HT-IBSS.
do you have the ability to use tracing? sudo trace-cmd -e iwlwifi The output will be very helpful. Thanks.
Hi Emmanuel, I've installed trace-cmd but the command you gave me doesn't work: sudo trace-cmd -e iwlwifi unknown command: -e trace-cmd version 1.0.3 usage: trace-cmd [COMMAND] ... commands: record - record a trace into a trace.dat file start - start tracing without recording into a file extract - extract a trace from the kernel stop - stop the kernel from recording trace data reset - disable all kernel tracing and clear the trace buffers report - read out the trace stored in a trace.dat file split - parse a trace.dat file into smaller file(s) listen - listen on a network socket for trace clients list - list the available events, plugins or options I tried replacing '-e' with the command 'extract' but that didn't work either: sudo trace-cmd extract iwlwifi Command start does not take any commands Did you mean 'record'? Sorry, I've never used trace-cmd before. I'm usually not working on the kernel level :(
sorry - obviously you are right sudo trace-cmd record -e iwlwifi -e iwlwifi_msg Then run the scenario until it crashes
BTW the output is trace.dat. It can be fairly large, please send it privately to my mail. Thanks
(also recommend to compress it - it compresses really well)
This bug has been root caused and will be fixed in later firmware releases.
please close as duplicate: https://bugzilla.kernel.org/show_bug.cgi?id=66001 there is more data there.
*** This bug has been marked as a duplicate of bug 66001 ***