Centrino Advanced-N 6200 Not Sustaining Wireless Connections

Bug #1360749 reported by Lonnie Lee Best
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
NetworkManager
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I'm having issues sustaining wireless connections with a HP Pavilion dv8t-1200 CTO Entertainment Notebook PC (Product# WF681AV):
http://support.hp.com/us-en/product/HP-Pavilion-dv8-1200-Entertainment-Notebook-PC-series/4150051/model/4190758/troubleshooting?cc=us&lang=en

wifi card: Centrino Advanced-N 6200

While it is connected it performs well, but it often becomes disabled and I have to toggle it back on using a touch-toggle-button located above the number pad of the keyboard.

When it becomes disabled, no wi-fi connections are listed under Ubuntu's network manager applet, but after toggling it back on, all the local wifi connections reappear.

Sometimes this will happen 4 times in a 10 minute span, and other times it will sustain the wifi connection for hours. I have experience this behavior on multiple wifi routers, even on ones giving 5 bars (located 10 feet away).

In summary, it seems like it is toggling off (as though I manually pressed the toggle button myself -- which is definitely not the case).

Laptop:

sudo dmidecode
Handle 0x0001, DMI type 1, 27 bytes
System Information
 Manufacturer: Hewlett-Packard
 Product Name: HP Pavilion dv8 Notebook PC
 Version: 0499220000241210001040000
 Wake-up Type: Power Switch
 SKU Number: WF681AV
 Family: 103C_5335KV

Wireless Adapter:

sudo lshw -C network
  *-network
       description: Wireless interface
       product: Centrino Advanced-N 6200
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlan0
       version: 35
       serial: 00:27:10:15:55:c0
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=3.13.0-34-generic firmware=9.221.4.1 build 25532 ip=192.168.1.2 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn
       resources: irq:47 memory:da100000-da101fff

sudo lspci | grep -i net
02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)

sudo dmidecode
Handle 0x0015, DMI type 41, 11 bytes
Onboard Device
 Reference Designation: Intel(R) Centrino(R) Advanced-N 6200 AGN
 Type: Ethernet
 Status: Enabled
 Type Instance: 1
 Bus Address: 0000:02:00.0

Certification Catalog Entry:
http://www.ubuntu.com/certification/catalog/component/pci/8086%3A4239/

Also found this wireless card listed here:
http://wireless.kernel.org/en/users/Drivers/iwlwifi

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-34-generic 3.13.0-34.60
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lonnie 2490 F.... pulseaudio
                      lonnie 8626 F.... pulseaudio
 /dev/snd/controlC0: lonnie 2490 F.... pulseaudio
                      lonnie 8626 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Aug 24 00:17:18 2014
HibernationDevice: RESUME=UUID=154ec9be-4204-4fe0-9dcd-3e13f4b66375
InstallationDate: Installed on 2014-07-30 (24 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=abe40f0f-3966-4481-8a33-1372af32a315 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-34-generic N/A
 linux-backports-modules-3.13.0-34-generic N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 7001
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 35.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr0499220000241210001040000:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv8 Notebook PC
dmi.product.version: 0499220000241210001040000
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :
information type: Public → Private
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/

Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :
Download full text (3.7 KiB)

I haven't tested newer kernels yet, but I may have fixed this by chosing the "Ignore" option for IPV6 in the Network-Manager.

I did this after seeing this in the logs:

Sep 17 20:52:40 computer1 kernel: [ 8708.176663] IPv6: wlan0: IPv6 duplicate address fe80::227:10ff:fe15:55c1 detected!

More Context:

Sep 17 20:52:39 computer1 NetworkManager[1184]: <info> (wlan0): supplicant interface state: associating -> associated
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Sep 17 20:52:40 computer1 wpa_supplicant[1613]: wlan0: WPA: Key negotiation completed with 00:23:69:6e:28:04 [PTK=CCMP GTK=TKIP]
Sep 17 20:52:40 computer1 wpa_supplicant[1613]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:23:69:6e:28:04 completed [id=0 id_str=]
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Video Surveillance'.
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> Activation (wlan0) Beginning IP6 addrconf.
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Sep 17 20:52:40 computer1 NetworkManager[1184]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Sep 17 20:52:40 computer1 avahi-daemon[1177]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.253.
Sep 17 20:52:40 computer1 avahi-daemon[1177]: New relevant interface wlan0.IPv4 for mDNS.
Sep 17 20:52:40 computer1 avahi-daemon[1177]: Registering new address record for 192.168.2.253 on wlan0.IPv4.
Sep 17 20:52:40 computer1 avahi-daemon[1177]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::227:10ff:fe15:55c1.
Sep 17 20:52:40 computer1 avahi-daemon[1177]: New relevant interface wlan0.IPv6 for mDNS.
Sep 17 20:52:40 computer1 avahi-daemon[1177]: Registering new address record for fe80::227:10ff:fe15:55c1 on wlan0.*.
Sep 17 20:52:40 computer1 kernel: [ 8708.176663] IPv6: wlan0: IPv6 duplicate address fe80::227:10ff:fe15:55c1 detected!
Sep 17 20:52:41 computer1 NetworkManager[1184]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Sep 17 20:52:41 computer1 NetworkManager[1184]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Sep 17 20:52:41 computer1 NetworkManager[1184]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 17 20:52:41 computer1 NetworkManager[1184]: <info> NetworkManager state is now CONNECT...

Read more...

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote : Re: Centrino Advanced-N 6200 Not Sustaining Wireless Connections for IPV4 if IPV6 is not set to Ignore
summary: - Centrino Advanced-N 6200 Not Sustaining Wireless Connections
+ Centrino Advanced-N 6200 Not Sustaining Wireless Connections for IPV4 if
+ IPV6 is not set to Ignore
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

My workaround of ignoring IPV6 no longer works in Ubuntu 15.04 with kernel 3.19.0-26-generic.

The drivers for the Centrino Advanced-N 6200 are terribly unstable.

description: updated
description: updated
summary: - Centrino Advanced-N 6200 Not Sustaining Wireless Connections for IPV4 if
- IPV6 is not set to Ignore
+ Centrino Advanced-N 6200 Not Sustaining Wireless Connections
description: updated
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

Earlier I mentioned that ignoring IPV6 is no longer a work-around. That's true.

Ignoring is no longer enough, I had to disable IPV6 entirely; here's how:

1) Use nano editor to open /etc/sysctl.conf:
sudo nano /etc/sysctl.conf

2) Then add these lines to the bottom:

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

3) Hit ctrl-o to save
4) reboot

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

Earlier, someone said that IPV6 has nothing to do with wifi drivers. Then, why is it that if IPV6 is enabled the wifi card can't maintain a connection?

Below is what happens in the logs after I turn on my wifi toggle switch (without IPV6 disabled):

Aug 19 22:37:13 lonnie-pc kernel: [ 2475.491038] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.
Aug 19 22:37:13 lonnie-pc NetworkManager[866]: <info> WiFi now enabled by radio killswitch
Aug 19 22:37:13 lonnie-pc kernel: [ 2475.494328] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
Aug 19 22:37:13 lonnie-pc kernel: [ 2475.501231] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
Aug 19 22:37:13 lonnie-pc kernel: [ 2475.718978] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
Aug 19 22:37:13 lonnie-pc kernel: [ 2475.725800] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1
Aug 19 22:37:01 lonnie-pc wpa_supplicant[1094]: rfkill: WLAN hard blocked
Aug 19 22:37:14 lonnie-pc wpa_supplicant[1094]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Aug 19 22:37:14 lonnie-pc wpa_supplicant[1094]: dbus: Failed to construct signal
Aug 19 22:37:14 lonnie-pc NetworkManager[866]: <warn> could not get interface properties: No readable properties in this interface.
Aug 19 22:37:14 lonnie-pc NetworkManager[866]: <info> (wlan0): supplicant interface state: starting -> ready
Aug 19 22:37:14 lonnie-pc NetworkManager[866]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Aug 19 22:37:14 lonnie-pc NetworkManager[866]: <warn> could not get interface properties: No readable properties in this interface.

After this, no wifi connect is established. Then if I disable IPV6, it works . . . ? ? ?

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

Now, none of my ipv6-disabling tricks are getting the Centrino Advanced-N 6200 to function on kernel 3.19.0-26-generic.

information type: Private → Public
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

This problem went away for a long while but it is back again in Ubuntu 16.04.1 on kernel 4.4.0-45

lsb_release -a ; head -n1 /etc/issue ; cat /etc/lsb-release ; uname -a ; getconf -a | grep -i 'long_bit' ; arch ; uname -m

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
Ubuntu 16.04.1 LTS \n \l
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
Linux pc 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
LONG_BIT 64
x86_64
x86_64

tags: added: xenial
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.