Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Wireles dropping out consistently

  1. #1

    Default Wireles dropping out consistently

    My wireless connection is quite unstable. Connections will persist for seemingly random intervals from 2 minutes - 1 hour, although more often closer to the former than the latter. When my connection drops, Network Manager does not recognize that the wireless network still exists, and wireless must be disabled and then re-enabled in Network Manager in order for the network to reappear.

    Output of /sbin/lspci:
    02:00.0 Network controller: Qualcomm Atheros AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01)

    Output of /sbin/lspci -n:
    02:00.0 0280: 168c:0024 (rev 01)

    Output of /usr/sbin/iwconfig:
    wls1 IEEE 802.11abgn ESSID:"2WIRE416"
    Mode:Managed Frequency:2.412 GHz Access Point: 74:9D:DC:21:79:81
    Bit Rate=36 Mb/s Tx-Power=18 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=64/70 Signal level=-46 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:45 Missed beacon:0

    It is important to note that this issue is *not* consistent across providers and/or routers. That is, I have only had this issue with two AT&T Uverse routers; other connections have persisted nicely. This leads me to believe, of course, that it is a router configuration issue. Therefore, I provide the following:

    Router Info:
    Manufacturer: Pace plc
    Model: 3801HGV

    If any further information would help, I would be happy to provide it.

    Any help would be greatly appreciated. Thank you!

    **EDIT** Sorry about the derp spelling in the title; missed that on my proofing
    Last edited by chi_julia; 09-Jan-2014 at 21:08. Reason: Typo

  2. #2

    Default Re: Wireles dropping out consistently

    Some additional information appearing in the Network Manager log around the time of the connection being dropped:

    2014-01-09T22:43:41.983171-06:00 linux-ebrl NetworkManager[17976]: <info> Activation (wls1) successful, device activated.
    2014-01-09T22:45:46.045580-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): supplicant interface state: completed -> 4-way handshake
    2014-01-09T22:45:46.054132-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): supplicant interface state: 4-way handshake -> completed
    2014-01-09T22:47:24.964244-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): supplicant interface state: completed -> 4-way handshake
    2014-01-09T22:47:24.973331-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): supplicant interface state: 4-way handshake -> completed
    2014-01-09T22:47:46.985252-06:00 linux-ebrl NetworkManager[17976]: <warn> Connection disconnected (reason -14)
    2014-01-09T22:47:46.986303-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): supplicant interface state: completed -> disconnected
    2014-01-09T22:47:46.987182-06:00 linux-ebrl NetworkManager[17976]: <warn> Connection disconnected (reason 14)
    2014-01-09T22:47:47.089877-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): supplicant interface state: disconnected -> scanning
    2014-01-09T22:48:01.816124-06:00 linux-ebrl NetworkManager[17976]: <warn> (wls1): link timed out.
    2014-01-09T22:48:01.817534-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): device state change: activated -> failed (reason 'SSID not found') [100 120 53]
    2014-01-09T22:48:01.860666-06:00 linux-ebrl NetworkManager[17976]: <info> NetworkManager state is now DISCONNECTED
    2014-01-09T22:48:01.861253-06:00 linux-ebrl NetworkManager[17976]: <warn> Activation (wls1) failed for connection '2WIRE416'
    2014-01-09T22:48:01.865645-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): device state change: failed -> disconnected (reason 'none') [120 30 0]
    2014-01-09T22:48:01.866194-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): deactivating device (reason 'none') [0]
    2014-01-09T22:48:02.073545-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): canceled DHCP transaction, DHCP client pid 20402
    2014-01-09T22:48:02.086064-06:00 linux-ebrl NetworkManager[17976]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    2014-01-09T22:48:03.429506-06:00 linux-ebrl NetworkManager[17976]: <info> (wls1): supplicant interface state: scanning -> inactive

  3. #3
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,357
    Blog Entries
    15

    Default Re: Wireles dropping out consistently

    On Fri 10 Jan 2014 04:16:01 AM CST, chi julia wrote:


    My wireless connection is quite unstable. Connections will persist for
    seemingly random intervals from 2 minutes - 1 hour, although more often
    closer to the former than the latter. When my connection drops, Network
    Manager does not recognize that the wireless network still exists, and
    wireless must be disabled and then re-enabled in Network Manager in
    order for the network to reappear.

    Output of /sbin/lspci:
    02:00.0 Network controller: Qualcomm Atheros AR5418 Wireless Network
    Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01)

    Output of /sbin/lspci -n:
    02:00.0 0280: 168c:0024 (rev 01)

    Output of /usr/sbin/iwconfig:
    wls1 IEEE 802.11abgn ESSID:"2WIRE416"
    Mode:Managed Frequency:2.412 GHz Access Point:
    74:9DC:21:79:81
    Bit Rate=36 Mb/s Tx-Power=18 dBm
    Retry long limit:7 RTS thrff Fragment thrff
    Power Managementff
    Link Quality=64/70 Signal level=-46 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:45 Missed beacon:0

    It is important to note that this issue is *not* consistent across
    providers and/or routers. That is, I have only had this issue with two
    AT&T Uverse routers; other connections have persisted nicely. This leads
    me to believe, of course, that it is a router configuration issue.
    Therefore, I provide the following:

    Router Info:
    Manufacturer: Pace plc
    Model: 3801HGV

    If any further information would help, I would be happy to provide it.

    Any help would be greatly appreciated. Thank you!

    **EDIT** Sorry about the derp spelling in the title; missed that on my
    proofing


    Hi
    Maybe some interference? A forum user created a python application
    wifiplotter to check things out;
    http://software.opensuse.org/package...rm=wifiplotter

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.6-4-desktop
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  4. #4
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: Wireles dropping out consistently

    On 01/09/2014 11:06 PM, chi julia wrote:
    >
    > Some additional information appearing in the Network Manager log around
    > the time of the connection being dropped:
    >
    > 2014-01-09T22:43:41.983171-06:00 linux-ebrl NetworkManager[17976]:
    > <info> Activation (wls1) successful, device activated.
    > 2014-01-09T22:45:46.045580-06:00 linux-ebrl NetworkManager[17976]:
    > <info> (wls1): supplicant interface state: completed -> 4-way handshake
    > 2014-01-09T22:45:46.054132-06:00 linux-ebrl NetworkManager[17976]:
    > <info> (wls1): supplicant interface state: 4-way handshake -> completed
    > 2014-01-09T22:47:24.964244-06:00 linux-ebrl NetworkManager[17976]:
    > <info> (wls1): supplicant interface state: completed -> 4-way handshake
    > 2014-01-09T22:47:24.973331-06:00 linux-ebrl NetworkManager[17976]:
    > <info> (wls1): supplicant interface state: 4-way handshake -> completed
    > 2014-01-09T22:47:46.985252-06:00 linux-ebrl NetworkManager[17976]:
    > <warn> Connection disconnected (reason -14)
    > 2014-01-09T22:47:46.986303-06:00 linux-ebrl NetworkManager[17976]:
    > <info> (wls1): supplicant interface state: completed -> disconnected
    > 2014-01-09T22:47:46.987182-06:00 linux-ebrl NetworkManager[17976]:
    > <warn> Connection disconnected (reason 14)


    Reason 14 for the disconnect is MIC failure. That is an uncommon reason. Rather
    than blaming the Atheros driver, I think the problem lies with the AT&T routers.
    Make certain that they have the latest firmware.

    If you have control over those routers, switch them from WPA1 to WPA2, or vice
    versa, depending on how they are set now. You might also try loading the module
    with the parameter "nohwcrypt=1". That will force the driver to perform the
    encryption/decryption in software, not in the hardware.



  5. #5

    Default Re: Wireles dropping out consistently

    Thanks very much for the suggestions! My problem appears to have been fixed.

    Details:
    The default authentication type for the router was WPA-PSK (TKIP) and WPA2-PSK (AES). Switching to WPA2-PSK (AES) only, the issue evaporated.

    It may also be useful to note that I discovered this morning that on an openSUSE installation on another machine, this problem did not occur. Therefore, there might be something deeper going on in the interaction between the driver, Network Manager, and the router.

    In any case, thank you very much for your help!
    Last edited by chi_julia; 10-Jan-2014 at 11:34. Reason: Fix fonts

  6. #6
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: Wireles dropping out consistently

    On 01/10/2014 12:36 PM, chi julia wrote:
    >
    > Thanks very much for the suggestions! My problem appears to have been
    > fixed.
    >
    > Details:
    > The default authentication type for the router was WPA-PSK (TKIP) and
    > WPA2-PSK (AES). Switching to WPA2-PSK (AES) only, the issue evaporated.
    >
    > It may also be useful to note that I discovered this morning that on an
    > openSUSE installation on another machine, this problem did not occur.
    > Therefore, there might be something deeper going on in the interaction
    > between the driver, Network Manager, and the router.


    Once a connection is made, NetworkManager is out of the loop, so the problem was
    between the router and the driver. I suppose it was possible that the router was
    getting confused and switching encryption mode in mid stream. That would
    certainly give the wrong MIC.

    In any case, AES is a lot more secure than TKIP. Good choice.



  7. #7

    Default Re: Wireles dropping out consistently

    Hi,
    Am new here and this seemed like the best place I found to post this. Seems to be issues with the search as I don't get results when I search this site for wireless. I had to go in and look through the threads to find this one.

    I seem to be having a similar issue to this, I can log in and usually 2 or 3 pages will load fine then it stops, If I log out and back in, same thing.
    This seems to have started about 2 weeks ago so am assuming it was caused from an update. I'm using a Windows XP VM to post this.

    lsusb
    Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter

    uname -r
    3.7.10-1.24-desktop

    Thanks for any help,
    Sean

  8. #8

    Default Re: Wireles dropping out consistently

    Not sure it this will help... can only post so much text.
    [ 7.823161] ieee80211 phy0: hwaddr 00:c0:ca:69:1e:86, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
    [ 7.837988] rtl8187: Customer ID is 0xFF
    [ 7.838019] Registered led device: rtl8187-phy0::radio
    [ 7.838041] Registered led device: rtl8187-phy0::tx
    [ 7.838063] Registered led device: rtl8187-phy0::rx
    [ 7.838210] ALSA mixer.c:889 5:2: cannot get min/max values for control 2 (id 5)
    [ 7.838480] rtl8187: wireless switch is on
    [ 7.838583] usbcore: registered new interface driver rtl8187
    [ 7.838680] usbcore: registered new interface driver snd-usb-audio
    [ 7.843731] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
    [ 7.844023] Registered led device: rt2800usb-phy1::radio
    [ 7.844042] Registered led device: rt2800usb-phy1::assoc
    [ 7.844054] Registered led device: rt2800usb-phy1::quality
    [ 7.844065] usbcore: registered new interface driver rt2800usb
    [ 8.145406] systemd-journald[311]: Received SIGUSR1
    [ 8.165961] Adding 20975612k swap on /dev/sdb2. Priority:-1 extents:1 across:20975612k
    [ 9.248319] ip6_tables: (C) 2000-2006 Netfilter Core Team
    [ 9.836020] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
    [ 9.838147] ip_tables: (C) 2000-2006 Netfilter Core Team
    [ 10.028279] e1000e 0000:03:00.0: irq 98 for MSI/MSI-X
    [ 10.128670] e1000e 0000:03:00.0: irq 98 for MSI/MSI-X
    [ 10.129151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 12.164567] fglrx_pci 0000:01:00.0: irq 100 for MSI/MSI-X
    [ 12.165100] <6>[fglrx] Firegl kernel thread PID: 1386
    [ 12.165153] <6>[fglrx] Firegl kernel thread PID: 1387
    [ 12.165203] <6>[fglrx] Firegl kernel thread PID: 1388
    [ 12.165274] <6>[fglrx] IRQ 100 Enabled
    [ 12.172038] <6>[fglrx] Reserved FB block: Shared offset:0, size:1000000
    [ 12.172040] <6>[fglrx] Reserved FB block: Unshared offset:fb70000, size:4000
    [ 12.172042] <6>[fglrx] Reserved FB block: Unshared offset:fb74000, size:484000
    [ 12.172043] <6>[fglrx] Reserved FB block: Unshared offset:fff8000, size:8000
    [ 12.172044] <6>[fglrx] Reserved FB block: Unshared offset:bfff4000, size:c000
    [ 12.420756] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 12.422556] NET: Registered protocol family 17
    [ 12.517474] e1000e: eth0 NIC Link is Up 10 Mbps Full Duplex, Flow Control: None
    [ 12.517479] e1000e 0000:03:00.0 eth0: 10/100 speed: disabling TSO
    [ 12.517544] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 13.552608] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 13.552622] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 13.552725] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 13.552738] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 13.852290] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 13.852336] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 14.147257] wlan0: authenticate with 00:1c:10:43:f9:3d
    [ 14.152770] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 14.152784] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 14.229312] wlan0: send auth to 00:1c:10:43:f9:3d (try 1/3)
    [ 14.231019] wlan0: authenticated
    [ 14.231088] rtl8187 1-5:1.0 wlan0: disabling HT/VHT due to WEP/TKIP use
    [ 14.231090] rtl8187 1-5:1.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
    [ 14.231092] rtl8187 1-5:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
    [ 14.231559] wlan0: associate with 00:1c:10:43:f9:3d (try 1/3)
    [ 14.234512] wlan0: RX AssocResp from 00:1c:10:43:f9:3d (capab=0x411 status=0 aid=1)
    [ 14.235506] wlan0: associated
    [ 14.235539] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 14.453188] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 14.453238] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 14.753748] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 14.753860] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 15.054310] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 15.054324] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 15.354806] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 15.354845] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 15.655308] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 15.655332] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 15.955790] ALSA hda_eld.c:337 HDMI: ELD buf size is 0, force 128
    [ 15.955822] ALSA hda_eld.c:356 HDMI: invalid ELD data byte 0
    [ 18.267842] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
    [ 18.706773] /dev/vmmon[2461]: Module vmmon: registered with major=10 minor=165
    [ 18.706777] /dev/vmmon[2461]: Module vmmon: initialized
    [ 18.714038] [2480]: VMCI: shared components initialized.
    [ 18.714077] [2480]: VMCI: host components initialized.
    [ 18.714148] [2480]: VMCI: Module registered (name=vmci,major=10,minor=58).
    [ 18.714152] [2480]: VMCI: Using host personality
    [ 18.714154] [2480]: VMCI: Module (name=vmci) is initialized
    [ 18.787428] ppdev: user-space parallel port driver
    [ 18.900911] netlink: 12 bytes leftover after parsing attributes.
    [ 18.900915] netlink: 12 bytes leftover after parsing attributes.
    [ 18.901013] netlink: 12 bytes leftover after parsing attributes.
    [ 18.901046] /dev/vmnet: open called by PID 2659 (vmnet-bridge)
    [ 18.901052] /dev/vmnet: hub 0 does not exist, allocating memory.
    [ 18.901067] /dev/vmnet: port on hub 0 successfully opened
    [ 18.901076] bridge-eth0: up
    [ 18.901079] bridge-eth0: attached
    [ 18.901107] netlink: 12 bytes leftover after parsing attributes.
    [ 18.901135] bridge-eth0: disabling the bridge on dev down
    [ 18.901164] bridge-eth0: down
    [ 18.901170] bridge-eth0: detached
    [ 18.901198] /dev/vmnet: open called by PID 2659 (vmnet-bridge)
    [ 18.901202] /dev/vmnet: hub 0 does not exist, allocating memory.
    [ 18.901213] /dev/vmnet: port on hub 0 successfully opened
    [ 18.901219] bridge-wlan0: device is wireless, enabling SMAC
    [ 18.901221] bridge-wlan0: up
    [ 18.901224] bridge-wlan0: attached
    [ 19.924407] /dev/vmnet: open called by PID 2713 (vmnet-netifup)
    [ 19.924416] /dev/vmnet: hub 1 does not exist, allocating memory.
    [ 19.924433] /dev/vmnet: port on hub 1 successfully opened
    [ 19.988907] /dev/vmnet: open called by PID 2716 (vmnet-dhcpd)
    [ 19.988917] /dev/vmnet: port on hub 1 successfully opened
    [ 19.992210] /dev/vmnet: open called by PID 2802 (vmnet-natd)
    [ 19.992216] /dev/vmnet: hub 8 does not exist, allocating memory.
    [ 19.992228] /dev/vmnet: port on hub 8 successfully opened
    [ 19.992277] netlink: 12 bytes leftover after parsing attributes.
    [ 19.992280] netlink: 12 bytes leftover after parsing attributes.
    [ 19.992364] netlink: 12 bytes leftover after parsing attributes.
    [ 19.992444] netlink: 12 bytes leftover after parsing attributes.
    [ 19.992919] userif-4: sent link down event.
    [ 19.992921] userif-4: sent link up event.<7>[ 19.994190] /dev/vmnet: open called by PID 2803 (vmnet-netifup)
    [ 19.994197] /dev/vmnet: port on hub 8 successfully opened
    [ 20.038122] /dev/vmnet: open called by PID 2807 (vmnet-dhcpd)
    [ 20.038136] /dev/vmnet: port on hub 8 successfully opened
    [ 27.908389] Bluetooth: Core ver 2.16
    [ 27.908409] NET: Registered protocol family 31
    [ 27.908410] Bluetooth: HCI device and connection manager initialized
    [ 27.908418] Bluetooth: HCI socket layer initialized
    [ 27.908420] Bluetooth: L2CAP socket layer initialized
    [ 27.908425] Bluetooth: SCO socket layer initialized
    [ 27.909958] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 27.909960] Bluetooth: BNEP filters: protocol multicast
    [ 27.909964] Bluetooth: BNEP socket layer initialized
    [ 303.509105] /dev/vmmon[4719]: PTSC: initialized at 3612234000 Hz using TSC, TSCs are synchronized.
    [ 303.683201] /dev/vmmon[4719]: Monitor IPI vector: 0
    [ 323.582646] usb 12-2: reset high-speed USB device number 2 using xhci_hcd
    [ 323.607973] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e40
    [ 323.607977] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e00
    [ 323.607978] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e80
    [ 323.607980] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4ec0
    [ 323.607981] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f00
    [ 323.607983] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f40
    [ 323.607984] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f80
    [ 323.673718] usb 3-2.3: reset high-speed USB device number 3 using ehci_hcd
    [ 327.030743] usb 12-2: reset high-speed USB device number 2 using xhci_hcd
    [ 327.056132] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e40
    [ 327.056135] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e00
    [ 327.056137] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e80
    [ 327.056138] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4ec0
    [ 327.056139] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f00
    [ 327.056141] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f40
    [ 327.056142] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f80
    [ 327.301109] usb 12-2: reset high-speed USB device number 2 using xhci_hcd
    [ 327.326601] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e40
    [ 327.326603] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e00
    [ 327.326605] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4e80
    [ 327.326606] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4ec0
    [ 327.326608] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f00
    [ 327.326609] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f40
    [ 327.326610] xhci_hcd 0000:06:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8808014d4f80
    [ 327.640957] usb 3-2.3: reset high-speed USB device number 3 using ehci_hcd
    [ 327.892485] usb 3-2.3: reset high-speed USB device number 3 using ehci_hcd
    [ 353.560489] NET: Registered protocol family 39
    [ 3823.482451] wlan0: deauthenticated from 00:1c:10:43:f9:3d (Reason: 16)
    [ 3823.482564] bridge-wlan0: disabling the bridge on dev down
    [ 3823.482593] bridge-wlan0: down
    [ 3823.482600] bridge-wlan0: detached
    [ 3823.482619] /dev/vmnet: open called by PID 2659 (vmnet-bridge)
    [ 3823.482626] /dev/vmnet: hub 0 does not exist, allocating memory.
    [ 3823.482639] /dev/vmnet: port on hub 0 successfully opened
    [ 3823.482646] bridge-eth0: up
    [ 3823.482648] bridge-eth0: attached
    [ 3823.528298] cfg80211: Calling CRDA to update world regulatory domain
    [ 3823.530361] cfg80211: World regulatory domain updated:
    [ 3823.530363] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 3823.530364] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 3823.530366] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [ 3823.530367] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [ 3823.530368] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 3823.530369] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 3823.682212] userif-4: sent link down event.
    [ 3823.682214] userif-4: sent link up event.<6>[ 3825.231456] wlan0: authenticate with 00:1c:10:43:f9:3d
    [ 3825.309334] wlan0: send auth to 00:1c:10:43:f9:3d (try 1/3)
    [ 3825.311347] wlan0: authenticated
    [ 3825.311404] rtl8187 1-5:1.0 wlan0: disabling HT/VHT due to WEP/TKIP use
    [ 3825.311407] rtl8187 1-5:1.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
    [ 3825.311408] rtl8187 1-5:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
    [ 3825.312079] wlan0: associate with 00:1c:10:43:f9:3d (try 1/3)
    [ 3825.314475] wlan0: RX AssocResp from 00:1c:10:43:f9:3d (capab=0x411 status=0 aid=1)
    [ 3825.315468] wlan0: associated
    [ 3825.334014] bridge-eth0: disabling the bridge on dev down
    [ 3825.334052] bridge-eth0: down
    [ 3825.334056] bridge-eth0: detached
    [ 3825.334074] /dev/vmnet: open called by PID 2659 (vmnet-bridge)
    [ 3825.334083] /dev/vmnet: hub 0 does not exist, allocating memory.
    [ 3825.334093] /dev/vmnet: port on hub 0 successfully opened
    [ 3825.334099] bridge-wlan0: device is wireless, enabling SMAC
    [ 3825.334101] bridge-wlan0: up
    [ 3825.334102] bridge-wlan0: attached
    [ 3825.533860] userif-4: sent link down event.
    [ 3825.533862] userif-4: sent link up event.

  9. #9

    Default Re: Wireles dropping out consistently

    I went into Yast and removed a hard wired network connection, when I saved the network configuration it seemed to refresh things as I got 2 pages to load and it stopped, just like logging out and back in.

    So, I disconnected my RTL8187 which I bought for Linux and connected my Hawking USB Wireless adapter I bought for Windows. Seems to work great, I connected the RTL8187 to my Windows XP VM and it works great, now I have good speeds on both.

    So, am back to assuming a driver update broke the RTL8187, sense this started about 2 weeks ago.
    1. Should I report this somewhere?

    I've had flash working also, but after an update it freezes my computer.
    2. I guess, I don't understand, are Opensuse users not supposed to update?

    Thanks,
    Sean

  10. #10
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: Wireles dropping out consistently

    On 01/26/2014 08:06 AM, WashingtonSean wrote:
    >
    > I went into Yast and removed a hard wired network connection, when I
    > saved the network configuration it seemed to refresh things as I got 2
    > pages to load and it stopped, just like logging out and back in.
    >
    > So, I disconnected my RTL8187 which I bought for Linux and connected my
    > Hawking USB Wireless adapter I bought for Windows. Seems to work great,
    > I connected the RTL8187 to my Windows XP VM and it works great, now I
    > have good speeds on both.
    >
    > So, am back to assuming a driver update broke the RTL8187, sense this
    > started about 2 weeks ago.
    > 1. Should I report this somewhere?
    >
    > I've had flash working also, but after an update it freezes my computer.
    > 2. I guess, I don't understand, are Opensuse users not supposed to
    > update?


    Of course openSUSE users are supposed to update, but you may have been hit by
    some unique failure in the update process itself. The reason I say this is that
    driver rtl8187 is quite old, and it changes very slowly. I reviewed the commit
    history for this driver in the mainline kernel and found the following:

    Oct. 29, 2013 - increase queue depth. This change doubles the number of
    preallocated entries in the receive queue. It only takes effect under extremely
    high input situations.

    Sep. 4, 2013 - fix potential memory leak in error path. This one has zero effect
    for the normal case where the device initializes with no error.

    Dec. 12, 2012 - internal change with compiler directives. This one was needed
    because some internal compiler directives were being eliminated. It would only
    affect compilation, and have no effect on execution.

    All other changes predate any updates to kernel 3.7. BTW, I run both RTL8187L
    and RTL8187B devices with no problems.

    Your wlan0 device is deauthenticating for reason 16, which is a group key
    timeout. Did you make any changes in the configuration or firmware of your AP
    that corresponds with this failure? Has the AP been rebooted recently?


Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •