Random Mass Disconnects
Hi I am after a bit of advice.
I have had inifinity for the past month and a half and all has been well apart from the odd disconnect. However this week I have started to have problems with periods of constant disconnecting, 1st was on the 9th July which lasted all evening with the disconnects happening every 1 to 5 minutes and again for an hour today. The bout today seemed to kick off with an incoming phonecall which seemed to have a lot of static, however ringing my line from my mobile during the disconnects resulted in a clear line but the disconnects persisted.
The weather has been fine both times in case it is important.
1. Product name:
BT Home Hub
2. Serial number:
3. Firmware version:
Software version 4.7.5.1.83.8.173.1.6 (Type A) Last updated 24/05/14
4. Board version:
BT Hub 5A
5. VDSL uptime:
0 days, 00:55:18
6. Data rate:
20000 / 76329
7. Maximum data rate:
27993 / 88978
8. Noise margin:
9.8 / 6.7
9. Line attenuation:
0.0 / 15.7
10. Signal attenuation:
0.0 / 15.8
This is info from my hub now, however during the disconnects the Noise margin drops to 6.0/6.0 for the short periods it works however speeds seem to be unaffected and I managed to get 75mb down 19 up as normal.
It looks like there is a fault somewhere however but as the fault seems to be intermittent I am not sure how much notice BT will take and I am wary of a call out charge if they decide there is no fault. I have checked the physical connections each time and all is secure. I do have a small white box by my master socket that the wiring goes through first although I am unsure as to it's purpose.
Any assistance is gratefully received.
Have you tried the "quiet line" test ? With a corded phone plugged into the test socket and dial 17070 and pick option 2. The line should be silent with no crackles, pops, or buzzing. Should you get anything other than a quiet line, then as imjolly says, you should dial 151 and report it but DO NOT mention the broadband otherwise they will go down the broadband route. A good broadband connection is dependant on having a good voice line.......
If you found this post helpful, then please click the star on the left, after all, I'm only trying to help........
Similar Messages
-
Mass disconnection : Error 44 in SM21
Hi<BR>
<BR>
I have a mass disconnection for my Japan users with the System Log (SM21) showing Error 44, and Error 5.<BR>
<BR>
Error 44 is Error in SNC layer (Secure Network Communication). I have checked the documentations and forums, it is usually caused by time synchronization between the server and client. However, we just did a time synchronization for all the servers 2 weeks ago. Are there other possible causes for Error 44?<BR>
<BR>
And for Error 5, I can hardly find any more detail information regarding this error, other than Internal Error. I have searched the SAP documentation and the forums, but there are no hits at all. Anyone can share their experiences in fixing this error?<BR>
<BR>
I have forgotten to add that this issue seems to happen around 5pm to 6pm.<BR>
<BR>
Thanks in advance.<BR>
Edited by: Roche SAP Support IBM on Mar 2, 2011 11:52 AMHi Ankit,
This problem usually occurs on Windows-based application servers that have a large number of configured work processes (more than 50). This problem cannot usually be reproduced. This response is caused by a long initialization phase of the work processes in the systems described above. You execute initialization of the work process in a critical section that is protected by a semaphore. If you perform a lock operation shortly after the system starts, the work process that executes this lock operation requests the same semaphore. If many work processes request this semaphore in the initialization, the system cannot perform the lock operation and it terminates with the syslog entry mentioned above. The problem no longer occurs after the work processes are initialized.
Regards,
Sachin Rane. -
[solved-ish] random usb disconnect
Hi
There's a first time for everything and today that seems to be a random USB disconnect.
So my USB dongle was disconnected and wouldn't reconnect when replugged.
Does this error message mean anything or should I be looking elsewhere to try and find the cause of the failure? Google hasn't turned up much of use and didn't see much on the forums here either.
Jul 1 18:18:53 localhost kernel: [193128.074045] usb 2-5: USB disconnect, device number 3
Jul 1 18:18:53 localhost kernel: [193128.074211] rtusb_disconnect: unregister usbnet usb-0000:00:1d.7-5
Jul 1 18:18:53 localhost kernel: [193128.074216] RtmpOSNetDevDetach(): RtmpOSNetDeviceDetach(), dev->name=ra0!
Any ideas?
Thanks for any help
EDIT seems to be some kind of hardware problem.
Last edited by Bazzaah (2012-07-02 17:25:52)Hi, a lot of people too (myself included). After upgrade, any usb unit goes away (some external devices like mouses excepted), usb pendrives dissapear (and become corrupted for any other computer), battery goes down quicklier and performance is affected. It seems 10.9.2 doesn't manage correctly hardware physical connections by asking them continuously. This is my young macbookair performance since I unfortunately upgraded to 10.9.2 four days ago. A lot of people is calling in all forums for questions (iphones, Cameras, external drives, monitors...) that are all related with this missfunction with physical connections.
MacBookAir 6,2
Intel Core i7
1,7 GHz
8 GB
ROM: MBA61.0099.B07
SMC: 2.13f7
OS X 10.9.2 (13C64)
kernel: Darwin 13.1.0 -
Wireless Lan Controller users randomly get disconnected
Hi to all,
We have issues where clients randomly get disconnected from the wireless network, i have a 4400 WLC with the version 4.2.176.0 and suddenly users are getting disconnected, what i've noticed is that the users are attached to one access point at 100% signal straight and at 54Mbps but suddenly the signal and the speed goes down and the client roams to another access point that is far away from the users location (the user never moves and is next to the access point that they should connect to).
It seems that the Auto RF algoritm is not working correctly, I upgrade to the 6.0.182.0 release but the problem still remains.
Any ideas of what else should i try??
Thanks in advanceFurther on this investigation is that we are using Intel based Wireless adapters in our laptops across the company. All adapters that support 802.11n specifications had issues, except one particular model X200 running Windows XP SP3. Intel has also come up with a fix for the 802.11n clients dropping their connectivity and it is available here:
http://www-307.ibm.com/pc/support/site.wss/MIGR-71056.html
The specific section on this page is as below:
Version 13.01.1000 (6MWC18WW)
(New) Added support for Intel WiFi Link 5150.
(Fix) Fixed an issue where wireless connection might be dropped in 802.11n mode.
Would be curious to know what type of Wireless NICs is everyone else using. What is the driver version? Driver date?
Thanks! -
UCCE 8.5 - Random Call Disconnect
Hi
Have an issue in UCCE 8.5 set up where in the calls are getting disconnected randomly while transferring to agents. (agent got reserved)
From the call server logs, I could see the following info::-
699077: 10.22.135.26: Feb 18 2013 14:27:40.439 +0530: %CVP_8_5_ICM-7-TRACE_GARBAGE_COLLECTOR: {Thrd=ICM Garbage Collector} ICMGarbageCollector:sendGEDDisconnect: ssId = SYS_SIP1, dialogueId: 34208, trkGrp = TRUNK GROUP [100] IDLE TRUNKS = 894 INBOUND TRUNKS = 130, trunk = 79, type = SIP_LEG, callId:1F2B04A878CF11E29B33E092CDE51CE9, callLegId = 1F2BA0D0-78CF11E2-9B36E092-CDE51CE9, dnis = 6300, ani = 9225332162uui =
699078: 10.22.135.26: Feb 18 2013 14:27:40.439 +0530: %CVP_8_5_ICM-7-CALL: {Thrd=ICM Garbage Collector} CALLGUID = 1F2B04A878CF11E29B33E092CDE51CE9, DLGID = 34208 [SIP_LEG] - Publishing ,, [ICM_EVENT_REPORT], dialogueId=34208, sendSeqNo=4, eventId=DISCONNECT, causeCode=MAINTENANCE(TIMEOUT),, LEGID = 1F2BA0D0-78CF11E2-9B36E092-CDE51CE9, DNIS = XXXX, ANI = 9225332162
Could someone explain me what does it says..??
Thanks in advance.
Regards,
JhonHello,
In the TCD (Termination Call Detail) table which you can find in the HDS database, you can find a column called "CallDisposition". This column contains codes that refer to how the call was ended (i.e. Call Disposition code of 52 refers to "Called Party Disconnected").
Reference: CTI Server Reference Guide
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/configuration/guide/ctisvr80.pdf
Also, you can find many posts on this forum relating to "Call Disposition" (i.e. https://supportforums.cisco.com/message/3490321)
1. If the customer disconnects the call, the Call disposition of the call(all 3 legs) will be 13.2. If the agent disconnects the call, the second call leg disposition is 52 and other 2 is 13
Hope this helps,
Justine. -
Firewire - Random Device Disconnects
I have a new iMAC24 that I've been having problems with regarding Firewire attached external drives. I've tried two new LaCie 320GB d2 Quadra drives and both would be ejected by the system shortly after waking the computer out of sleep mode; this could routinely repeated and I returned both drives my local computer shop. Before returning the second drive I actually did a complete reinstall of Leopard on my iMAC which didn't help the problem.
I also have an older LaCie drive (the model is not printed on the case) which works a bit better. I gets disconnected as well, but uniquely enough it immediately reconnects itself. In this case the disconnects happen randomly at 30 to 60 minute intervals; I finally just turned the drive off.
I've tried numerous cables and port combinations with no improvement. In conversations with other Apple users at my local Apple store and 3rd party retailer I've found that others have had similar problems and simply live with it.
Is this just a problem to be tolerated or is there a know Firewire / iMAC combo out there that is absolutely known to work (i.e. the drive stays connected over time)?
Thanks,
DonIn case anyone is curious, this problem still exists with audio devices that use Apple's firewire drivers. So, if you use Apogee, Yamaha, etc, you're still getting random audio offsets via firewire.
Motu is not affect since it uses its own drivers. -
Intel wireless chipset clients random Citrix disconnects
Currently using intel 5100 & 6200 client cards on multiple driver versions. WiSM is 7.0.116. APs are 1250 and 1260 series. Citrix is setup to send server-side keepalives for session reliability. Randomly, several times a day the client will get disconnected from the Citrix application session but maintain connectivity to the AP and other applications continue to work. Traces show the server-side keepalive reach the controller but are delayed from controller to client by 5-6 seconds. Just enough time for the Citrix server to timeout and tear down to session. Additional testing shows the delay most likely occurs somewhere from controller to AP. It occurs on multiple controllers on multiple campuses.
We have Dell/Broadcom clients that don't experience the problem. The only commonality seems to be the Intel cards. Any ideas? CCX? I know Intel has a special relationship with Cisco regarding CCX and have developed features not available on other cards. Tried disabling power save and other CCX features but hasn't solved the issue. Any ideas are appreciated on this very strange problem.
Thanks!
Sent from Cisco Technical Support iPhone AppUpdate to this issue. I've found the 5 second delay actually is occurring on the AP. Packets traverse normally through the entire network but randomly delayed at the AP. TAC is looking at it but no cause found yet. Also verified this seems to occur only with Intel wireless chipsets. Others (Broadcom etc.) don't experience the problem.
Sent from Cisco Technical Support iPhone App -
WRT1900AC Random Wireless Disconnects
Anyone with this modem experience random wireless drops that last a few seconds? At least once a day, usually late night, everything connected via wireless loses connectivity for a few seconds then reconnects. Both 2.4 and 5Ghz go down simultaneously.
Here is my router info:
Router Information
Firmware Version: 1.1.7.160177
Serial Number:
Current Router Time: Wednesday, 23 April 2014 14:44:28 (GMT -07:00)
Current Browser Time: Wednesday, 23 April 2014 14:44:29 (GMT -07:00)
Internet MAC Address:
Server Name: ScogreraWiFi
Host Name: ScogreraWiFi
Domain Name:
Linksys Smart Wi-Fi Services
Status: Connected
Internet Connection (IPv4)
Connection Type: PPPoE
Login Status: Connected
Internet Address: 206.80.218.50
Subnet Mask: 255.255.255.255
Default Gateway: 67.40.227.67
DNS1: 205.171.3.65
DNS2: 205.171.2.65
DNS3:
MTU: 1480
DHCP Lease Time:
Internet Connection (IPv6)
Connection Type: Disconnected
Internet Address:
Default Gateway:
DNS1:
DNS2:
DNS3:
DHCP Lease Time:
Local Network
Local MAC Address:
IPv4 Address: 10.2.1.1
IPv4 Subnet Mask: 255.255.255.0
IPv6 Link-Local Address:
Prefix Address:
DHCP Server
DHCP Server: Enabled
Start IP Address: 10.2.1.10
End IP Address: 10.2.1.59
Client lease time: 1440
Static DNS 1: 10.2.1.2
Static DNS 2:
Static DNS 3:
WINS:
2.4 GHz Wireless Network
Status: Enabled
MAC Address:
Mode: 802.11bgn
Network Name (SSID): ScogreraWiFi2.4
Channel Width: 20 MHz
Channel: Auto
Security: WPA2/WPA Mixed Personal
5 GHz Wireless Network
Status: Enabled
MAC Address:
Mode: 802.11an
Network Name (SSID): ScogreraWiFi
Channel Width: Auto
Channel: Auto
Security: WPA2/WPA Mixed PersonalI've had this same problem for the last few months. Called support last week and tech said it was probably channel conflict. Not sure why channel conflict would take the entire wireless down though... Tech recommended that .ac technology is not for everybody and that I would be more satisfied with older n series router?!?! He opened a case and said I should call customer support and ask to RMA the router I have and purchase an n series router or the new ac router Linksys just announced. Just spoke with another tech and she wanted to charge me for additional support. This is exactly what I was afraid of when Belkin purchased Linksys! I'll be ripping out my current router and purchasing another brand. Sorry just realized this should be posted under the EA6900ac post. Still dissapointed wtih Linksys.
-
WRT54GS with SpeedBooster random internet disconnects
Hi all I'm new to the forums,
I have an issue with the WRT54GS router i bought a few days ago, my 2 desktop computers are wired connected, where as my laptop, xbox 360 and wii are wireless. Everything is connected correctly and the internet works, but at random times (from 10min - 1hr) the internet disconnects on me. I had to turn off the router and turn it back on to get the internet back, then again at random times it disconnects on me again and i have to repeat the process over again. Is there anyway to fix this? I've downloaded the latest firmware drivers from this site, V6 i think. Plz help me! i want to play xbox live without thisHi… Reduce the MTU on this router to 1365. If you have DSL and you have configured PPPoE connection then make sure that you have selected “Keep Alive” option. For Xbox you need to assign a static IP on it and forward the ports 88 and 3074 for its IP address.
-
I'm using OS LIOn connect thru wireless connection.
I have frequent and random disconnect and connection loose, which need to reboot the box to recover the connection.
Does someone have a solution ?
Apple assistance isn't able to provide a fix
Regards1. Try updating the router firmware.
2. Try connecting to other routers e.g. starbucks or local library -
[SOLVED] Random wifi disconnects with BCM43228
Hi all,
I am having some trouble with the broadcom-wl driver. Below is from the journal. Highlights include:
Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:42:43 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 08:17:35:9d:40:60 timed out.
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=08:17:35:9d:40:60 reason=3 locally_generated=1
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
Does anyone know something I could try to fix this problem?
Thanks in advance,
Sam
Full log:
Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
Mar 18 09:42:05 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
Mar 18 09:42:05 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
Mar 18 09:42:05 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
Mar 18 09:42:08 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
Mar 18 09:42:08 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
Mar 18 09:42:10 mainsail sudo[795]: pam_unix(sudo:session): session closed for user root
Mar 18 09:42:15 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
Mar 18 09:42:17 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> associating
Mar 18 09:42:17 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
Mar 18 09:42:27 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 18 09:42:30 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:42:30 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:42:32 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
Mar 18 09:42:33 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
Mar 18 09:42:43 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
Mar 18 09:42:43 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
Mar 18 09:42:43 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
Mar 18 09:42:58 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
Mar 18 09:42:58 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
Mar 18 09:42:58 mainsail NetworkManager[356]: <info> Marking connection 'tempest' invalid.
Mar 18 09:42:58 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
Mar 18 09:42:58 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:42:58 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 18 09:42:58 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
Mar 18 09:42:58 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:42:59 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
Mar 18 09:43:00 mainsail dbus[362]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Mar 18 09:43:00 mainsail dbus[362]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Mar 18 09:43:09 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
Mar 18 09:43:09 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
Mar 18 09:44:28 mainsail systemd[417]: Time has been changed
Mar 18 09:44:28 mainsail systemd[1]: Time has been changed
Mar 18 09:44:59 mainsail dbus[362]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Mar 18 09:44:59 mainsail dbus[362]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Mar 18 09:45:07 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
Mar 18 09:45:07 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
Mar 18 09:46:59 mainsail dbus[362]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Mar 18 09:46:59 mainsail dbus[362]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
Mar 18 09:47:58 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> scanning
Mar 18 09:48:00 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> associating
Mar 18 09:48:10 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
Mar 18 09:48:10 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
Mar 18 09:48:10 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
Mar 18 09:48:23 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
Mar 18 09:48:23 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
Mar 18 09:48:23 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
Mar 18 09:48:23 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:48:23 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 18 09:48:23 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
Mar 18 09:48:23 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:48:25 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
Mar 18 09:48:26 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
Mar 18 09:48:36 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
Mar 18 09:48:36 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
Mar 18 09:48:36 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
Mar 18 09:48:51 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
Mar 18 09:48:51 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
Mar 18 09:48:51 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
Mar 18 09:48:51 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 18 09:48:51 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
Mar 18 09:48:51 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:48:51 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:48:52 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
Mar 18 09:48:54 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
Mar 18 09:48:55 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
Mar 18 09:48:55 mainsail dhcpcd[407]: eno1: DHCPv6 REPLY: No addresses available for this interface.
Mar 18 09:48:59 mainsail dbus[362]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Mar 18 09:48:59 mainsail dbus[362]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Mar 18 09:49:04 mainsail NetworkManager[356]: <warn> Connection disconnected (reason -3)
Mar 18 09:49:04 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
Mar 18 09:49:04 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
Mar 18 09:49:19 mainsail NetworkManager[356]: <warn> Activation (wlp2s0/wireless): association took too long, failing activation.
Mar 18 09:49:19 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: config -> failed (reason 'supplicant-timeout') [50 120 11]
Mar 18 09:49:19 mainsail NetworkManager[356]: <warn> Activation (wlp2s0) failed for connection 'tempest'
Mar 18 09:49:19 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:49:19 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 18 09:49:19 mainsail NetworkManager[356]: <info> (wlp2s0): deactivating device (reason 'none') [0]
Mar 18 09:49:19 mainsail NetworkManager[356]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Mar 18 09:49:20 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> inactive
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Auto-activating connection 'tempest'.
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) starting connection 'tempest'
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0/wireless): connection 'tempest' requires no security. No secrets needed.
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Config: added 'ssid' value 'tempest'
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Config: added 'scan_ssid' value '1'
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Config: added 'key_mgmt' value 'NONE'
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> Config: set interface ap_scan to 1
Mar 18 09:49:22 mainsail wpa_supplicant[398]: Successfully initialized wpa_supplicant
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-ASSOC-REJECT status_code=16
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:d7:0b:35:40 (SSID='tempest' freq=2412 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-ASSOC-REJECT status_code=16
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 08:17:35:9d:40:60 timed out.
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=08:17:35:9d:40:60 reason=3 locally_generated=1
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 08:17:35:9d:40:60 timed out.
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=08:17:35:9d:40:60 reason=3 locally_generated=1
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-ASSOC-REJECT status_code=16
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="tempest"
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:38:18:3d:80 (SSID='tempest' freq=2462 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-ASSOC-REJECT status_code=16
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=2 duration=20
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: inactive -> associating
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:d7:0b:35:40 (SSID='tempest' freq=2412 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 00:0e:d7:0b:35:40 timed out.
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:0e:d7:0b:35:40 reason=3 locally_generated=1
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:38:18:3d:80 (SSID='tempest' freq=2462 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 00:0e:38:18:3d:80 timed out.
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:0e:38:18:3d:80 reason=3 locally_generated=1
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 00:0e:38:18:3d:80 (SSID='tempest' freq=2462 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 00:0e:38:18:3d:80 timed out.
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:0e:38:18:3d:80 reason=3 locally_generated=1
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Trying to associate with 08:17:35:9d:40:60 (SSID='tempest' freq=2412 MHz)
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Authentication with 08:17:35:9d:40:60 timed out.
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=08:17:35:9d:40:60 reason=3 locally_generated=1
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tempest" auth_failures=1 duration=10
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: CTRL-EVENT-SCAN-STARTED
Mar 18 09:49:22 mainsail wpa_supplicant[398]: wlp2s0: Reject scan trigger since one is already pending
Mar 18 09:49:22 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
Mar 18 09:49:32 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
Mar 18 09:49:34 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: scanning -> associating
Mar 18 09:49:34 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: associating -> disconnected
Mar 18 09:49:44 mainsail NetworkManager[356]: <info> (wlp2s0): supplicant interface state: disconnected -> scanning
Last edited by Chocobo (2014-03-20 16:40:50)Here is my list of modules:
[swinchen@mainsail images]$ lsmod
Module Size Used by
rfcomm 50698 12
bnep 13053 2
nls_cp437 5953 1
vfat 10055 1
fat 51896 1 vfat
intel_rapl 11776 0
x86_pkg_temp_thermal 6991 0
intel_powerclamp 8802 0
coretemp 6358 0
kvm_intel 131500 3
kvm 396221 1 kvm_intel
crct10dif_pclmul 4682 0
btusb 19648 0
bluetooth 326343 32 bnep,btusb,rfcomm
crct10dif_common 1372 1 crct10dif_pclmul
uvcvideo 72804 0
crc32_pclmul 2923 0
videobuf2_vmalloc 3304 1 uvcvideo
videobuf2_memops 2335 1 videobuf2_vmalloc
videobuf2_core 28243 1 uvcvideo
crc32c_intel 14185 0
videodev 111840 2 uvcvideo,videobuf2_core
media 11719 2 uvcvideo,videodev
ghash_clmulni_intel 4405 0
aesni_intel 45548 0
aes_x86_64 7399 1 aesni_intel
lrw 3565 1 aesni_intel
gf128mul 5858 1 lrw
glue_helper 4417 1 aesni_intel
joydev 9631 0
ablk_helper 2004 1 aesni_intel
mousedev 10247 0
lib80211_crypt_tkip 8922 0
cryptd 8409 3 ghash_clmulni_intel,aesni_intel,ablk_helper
wl 4138002 0
dell_wmi 1485 0
sparse_keymap 3146 1 dell_wmi
i915 725997 4
lib80211 3821 2 wl,lib80211_crypt_tkip
ppdev 7118 0
iTCO_wdt 5407 0
iTCO_vendor_support 1929 1 iTCO_wdt
cfg80211 408199 1 wl
intel_agp 10872 1 i915
dell_laptop 12389 0
intel_gtt 12664 2 i915,intel_agp
dcdbas 6463 1 dell_laptop
drm_kms_helper 35710 1 i915
microcode 15216 0
evdev 11045 34
serio_raw 5009 0
drm 239102 5 i915,drm_kms_helper
psmouse 88171 0
rfkill 15651 5 cfg80211,bluetooth,dell_laptop
i2c_i801 11269 0
i2c_algo_bit 5391 1 i915
snd_hda_codec_hdmi 36379 1
i2c_core 24760 6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev
snd_hda_codec_idt 43694 1
ac 3334 0
wmi 8251 1 dell_wmi
snd_hda_intel 37352 3
thermal 8556 0
battery 7565 0
parport_pc 19479 0
parport 30517 2 ppdev,parport_pc
snd_hda_codec 150017 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
video 11457 1 i915
button 4605 1 i915
e1000e 222900 0
shpchp 25425 0
mei_me 9552 0
mei 62867 1 mei_me
snd_hwdep 6332 1 snd_hda_codec
lpc_ich 13368 0
ptp 8244 1 e1000e
pps_core 8833 1 ptp
snd_pcm 77822 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
processor 24577 0
snd_page_alloc 7298 2 snd_pcm,snd_hda_intel
snd_timer 18718 1 snd_pcm
snd 59029 13 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5418 1 snd
ext4 473451 2
crc16 1359 2 ext4,bluetooth
mbcache 6074 1 ext4
jbd2 80912 1 ext4
sd_mod 31361 5
sr_mod 14930 0
cdrom 34880 1 sr_mod
hid_generic 1153 0
hid_logitech_dj 10631 0
usbhid 40545 0
hid 90902 4 hid_generic,usbhid,hid_logitech_dj
atkbd 16806 0
libps2 4187 2 atkbd,psmouse
sdhci_pci 12604 0
sdhci 28820 1 sdhci_pci
mmc_core 95465 2 sdhci,sdhci_pci
ahci 23144 4
libahci 21698 1 ahci
i8042 13366 2 libps2,dell_laptop
serio 10721 6 serio_raw,atkbd,i8042,psmouse
libata 172104 2 ahci,libahci
scsi_mod 132250 3 libata,sd_mod,sr_mod
ehci_pci 3928 0
xhci_hcd 144553 0
ehci_hcd 64363 1 ehci_pci
usbcore 180208 6 btusb,uvcvideo,ehci_hcd,ehci_pci,usbhid,xhci_hcd
usb_common 1648 1 usbcore
I see have dell_wmi and wmi. Any idea why those might cause a problem? I will blacklist them and see if my problem improves.
Thanks for the reply.
EDIT: I am using a Dell Latitude E6430s
Last edited by Chocobo (2014-03-19 17:08:54) -
Random mass app crashing, need advice
Once in a while all my purchased applications would start crashing (quitting on startup). What's strange is that all of the stock apps that came with the iPhone would be fine but everything else is not. The only thing that would work in that case for me is deleting all the apps and restoring them from iTunes. But these mass crashes seem to be getting more frequent now so I was wondering if there is anything I could try doing to prevent this from happening. I entertained the idea of reverting to the original stock settings and effectively reinstalling everything but I'm not sure if that would help, would it? Is there anything else I could try before doing that?
Reboot the phone every now and then. It is just a computer and a new OS at that. It does (and will for a while) have bugs and memory leaks. Turning off and on is not rebooting. Turning off is just like "hibernate" on a laptop. So when you turn it back on, all that was in memory gets reloaded including issues.
Press and hold both the home and lock button. Keep holding both and ignore the slide to turn off message that will appear. Keep holding until you see the Apple Logo. This will do a full reboot of the phone. -
IChat to iChat random video disconnect.
Hi, I'm currently having to ichat with my girlfriend in the USA from here in London. And all of a sudden we're getting disconnected when we video chat every 20 minutes or so. We can connect to each other again immediately after, but the same thing keeps happening over and over again.
I run an iMac with Leopard, she runs a Macbook with Leopard.
We both have the same Router (Netgear WGR614V9 Wireless Router)
Both of our settings under iChat are as follows:
Port: 443
Server: slogin.oscar.aol.com
I'd really appreciate any help. iChat is like a staple in our keeping in touch right now.Are there any other symptoms before you lose contact ?
Any issues getting Mail or web browsing looking slow to get apge now and then ?
9:06 PM Saturday; January 10, 2009 -
G700 random wifi disconnections
Hi,
I have a G700 with windows 8 and I have noticed many wifi disconnections, from my home but also from other places where I can connect. So I'm know sure that it is not a problem with my home wifi connection...
I have just a few knowledge about windows 8 and don't know exactly what to do to fix this problem...
thank you for your helphi Missparker
Welcome to Lenovo Community Forums!
"Given that you have already did a Router modem Power cycle and still the same results and you have a working LAN connection to download some drivers"
1.
Open System Properties and go to Advanced System Settings
Then this
Spoiler
Now on the options
do this
Spoiler
2.
Download the driver based on you Wificard model
WLAN Driver (Broadcom, Qualcomm)
run the Downloaded file and just go ahead with it till it finishes the installation.
3. Open device Manager / Under Network Adapter, right click on WLAN device and select update driver
Now on the pop up window select "Browse my computer for driver software
Then select "Let me pick from a list"
You will be provided with a list of driver
Now select a driver and Check your Wireless connectivity
If it shows the same behavior
repeat step 3 and select another driver
and see how it goes.
Please Let me know your findings
Cheers!
Solid Cruver
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter! -
Hi,
We have GW Messenger 2.0.2 and we keep getting logged out and straight back
in again, throughout the day, with no particular pattern. We have quite alot
of users now, so it gets very annoying, as people keep being notified that
users go offline then come back on almost straight away.
Is there a sensitivity setting that disconnects the clients?
I cant find any errors apart from the following (unrelated?) message on the
console...
10:19:57 704 SPL Request (Get Other Status) [0xB106]:
CN=USERNAME,OU=CONTAINER,O=ORGUNIT - Host is unknown to system
HELP! This is very frustrating as it is getting reported to me almosy daily
by people, and as yet, I can't give them any solution apart from "ignore it"
Thanks
AlanI am having the same issue. The system has approx 800 users, and prior to upgrading to version 2.x I never had this problem.
It usually happens around 8:00AM when the bulk of the logins happen.
Any suggestions ?
Cody
>>> On 9/3/2007 at 2:21 AM, in message <XmQCi.3825$[email protected]>, Alan Thompson<[email protected]> wrote:
Hi,
We have GW Messenger 2.0.2 and we keep getting logged out and straight back
in again, throughout the day, with no particular pattern. We have quite alot
of users now, so it gets very annoying, as people keep being notified that
users go offline then come back on almost straight away.
Is there a sensitivity setting that disconnects the clients?
I cant find any errors apart from the following (unrelated?) message on the
console...
10:19:57 704 SPL Request (Get Other Status) [0xB106]:
CN=USERNAME,OU=CONTAINER,O=ORGUNIT - Host is unknown to system
HELP! This is very frustrating as it is getting reported to me almosy daily
by people, and as yet, I can't give them any solution apart from "ignore it"
Thanks
Alan
Maybe you are looking for
-
Hi, I have a couple of questions. 1. I see there are a few fields missing on the line item level on FB60. It's not the case for development or testing environment. But in Production it's happening. Does anyone know how to get these fields back? 2. Is
-
While running the application getting an error message send failed.(ie) not able to access the java class using the object defined in the remote config.
-
To Remove decimal digit in number field
Hi experts any one can tell me the function in Crystal Report for removing decimal digits in a number type field. like field value is 34.00 should be 34. Regards Gorge
-
I recently updated the reader to the latest version and have found that the zoom level is now inaccurate (e.g. it says 100% when the pdf is really being viewed at about 110%). So when I view my pdfs at 100% the graphics now appear all blurry, but whe
-
Aperture 2.1.4 issue with Image preview (Browser Only)
Hi, I'm using Aperture from some time, from past few days I'm facing issue with my aperture image browser only. i have few projects created. In some projects I'm unable to see the images in view browser only mode. If I select some other view option i