You are not logged in.
- Topics: Active | Unanswered
#1 2014-11-05 14:45:11
- DSK
- Member
- Registered: 2014-10-15
- Posts: 9
Wifi Connection Issue (Doesn't stay connected)
I am fairly new to Arch and I am having almost no troubles but one.
I can log in to Arch and connect to my Wifi without problem on boot but something is happening that I can't pinpoint where suddenly the connection stops. If I disconnect and try to reconnect it will time out. The only way for me to get wifi back is on a fresh boot.
The time varies. I could lose my connection in 5 minutes or 24 hours but when I lose it, its gone until next boot.
I notice problems occur more frequently if I am running more than one internet connected application (ex: Firefox and qBittorrent / Firefox OpenVPN / OpenVPN and VirtualBox ). In otherwords, it's not isolated to just a specific set of software.
I've been dealing with this for about three weeks trying to find out the root of the problem but I am not exactly sure where to look.
Does any one have a good suggestion or experienced a similar issue?
My Build:
External USB connected SSD - plain (not a virtual machine)
Arch x86_64
Linux 3.17
Network Manager
DHCP enabled at boot via systemctl
journaling is off (per SSD r/w usage)
Last edited by DSK (2014-11-15 19:28:05)
Offline
#2 2014-11-05 17:54:46
- MoonSwan
- Member
- From: Great White North
- Registered: 2008-01-23
- Posts: 881
Re: Wifi Connection Issue (Doesn't stay connected)
What type of wifi card is it? What kind of network is this? E.G. home behind a router and modem or connected via a smart phone with a USB tether? Are you using dhcp and, if you are, have you tried to use a static IP address?
Last edited by MoonSwan (2014-11-05 17:55:02)
Offline
#3 2014-11-06 13:32:28
- DSK
- Member
- Registered: 2014-10-15
- Posts: 9
Re: Wifi Connection Issue (Doesn't stay connected)
The hardware varies dependent on the host computer I am using. (Arch is installed on a mSATA connected via USB) Primarily, is a Marvell Avastar connected to a router at home.
Yes, I have dhcpcd enabled at boot. No static IP, as my system is removable, I left it as dynamic considering the network I may be on.
I will try a static address when I am home to see if this helps.
I read these two wikis as a result of your questions to gather more info:
https://wiki.archlinux.org/index.php/Dhcpcd
https://wiki.archlinux.org/index.php/Ne … IP_address
Let's see what happens with this.
Offline
#4 2014-11-06 16:38:50
- TheSaint
- Member
- From: my computer
- Registered: 2007-08-19
- Posts: 1,532
Re: Wifi Connection Issue (Doesn't stay connected)
The hardware varies dependent on the host computer I am using. (Arch is installed on a mSATA connected via USB)
Is a plain installation or in a virtualbox?
Do you have any log that we may look at?
do it good first, it will be faster than do it twice the saint 
Offline
#5 2014-11-06 16:59:19
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 20,353
Re: Wifi Connection Issue (Doesn't stay connected)
I would, whilst it is working, look at (and save) the output of
ip addr
ip route
iw list
and
iw theaNameOfYourWirelessInterface info
When it breaks, do those again and see what changed. Also, comb the output of ajournalctl and dmesg looking for clues.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
#6 2014-11-10 17:37:29
- DSK
- Member
- Registered: 2014-10-15
- Posts: 9
Re: Wifi Connection Issue (Doesn't stay connected)
Sorry for the late reply, just been busy and also took a few days to test out some changes. Not sure if I want to say this problem is SOLVED just yet. I did make some changes to dhcpcd at home and by making it static, as far as I can tell at this point, it seems to have resolved two issues. I have had a stable internet for two days (thus far at home) and I don't have a DNS leak anymore (I didn't mention this problem.)
@TheSaint:
My install is plain, direct on the mSATA, its just that I have a Windows install on a VM. Which is why I mentioned VirtualBox. So, the Windows VM is on the plain install Arch mSATA. Hopefully, this relieves some confusion.
@ewaller:
I would do this if it breaks again. So far my home connection has stayed connected with a static IP. I will also see what happens when I have time at work to see what the results are on a different network.
Now, I am curious what modifications would need to be made if I used a different wifi connection (work or a public access point) and still be able to connect and stay connected.
Last edited by DSK (2014-11-10 17:40:19)
Offline
#7 2014-11-11 14:59:20
- DSK
- Member
- Registered: 2014-10-15
- Posts: 9
Re: Wifi Connection Issue (Doesn't stay connected)
Seems I spoke too soon. After I rebooting back into Arch I had the same problem. I did no further configuration once I thought I had a solution. It has become clearer that general browsing doesn't effect the connections. Seems I can browse all day and night without a fuss. Atleast this has been my experience as of yet.
However, on a fresh boot with working wifi, I can log into my Virtualbox VM and have working wifi inside the VM for a few minutes and then it is broken (and very consistent on breaking the connection and rather quickly)
OpenVPN from Arch directly connects still but the times vary drastically but it will eventually break the connection.
These are the output files. I looked through them a few times already myself and seem to be identical (unless I have blindly overlooked something.) The only difference I did notice was the lease time (not sure if it is suppose to have a lease time if the dhcp is static.
I grouped these by command. The first is the working connection, the second is the broken connection.
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: mlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc mq state UP group default qlen 1000
link/ether 28:18:78:35:90:55 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.11/24 brd 192.168.1.255 scope global dynamic mlan0
valid_lft 3403sec preferred_lft 3403sec
inet6 fe80::2a18:78ff:fe35:9055/64 scope link
valid_lft forever preferred_lft forever
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: mlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc mq state UP group default qlen 1000
link/ether 28:18:78:35:90:55 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.11/24 brd 192.168.1.255 scope global dynamic mlan0
valid_lft 3240sec preferred_lft 3240sec
inet6 fe80::2a18:78ff:fe35:9055/64 scope link
valid_lft forever preferred_lft forever**Here is the only difference I noticed. What looks to be lease times for inet.
ip route
default via 192.168.1.1 dev mlan0 proto static metric 1024
192.168.1.0/24 dev mlan0 proto kernel scope link src 192.168.1.11
default via 192.168.1.1 dev mlan0 proto static metric 1024
192.168.1.0/24 dev mlan0 proto kernel scope link src 192.168.1.11 **identical
iw list
Wiphy phy0
max # scan SSIDs: 10
max scan IEs length: 256 bytes
Fragmentation threshold: 2346
RTS threshold: 2347
Retry short limit: 9
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* P2P-client
* P2P-GO
Band 1:
Capabilities: 0x37e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 3-streams
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15, 32
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps
* 5.5 Mbps
* 11.0 Mbps
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (20.0 dBm) (no IR)
Band 2:
Capabilities: 0x37e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 3-streams
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15, 32
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5040 MHz [8] (disabled)
* 5060 MHz [12] (disabled)
* 5080 MHz [16] (disabled)
* 5170 MHz [34] (disabled)
* 5190 MHz [38] (20.0 dBm) (no IR)
* 5210 MHz [42] (20.0 dBm) (no IR)
* 5230 MHz [46] (20.0 dBm) (no IR)
* 5180 MHz [36] (20.0 dBm) (no IR)
* 5200 MHz [40] (20.0 dBm) (no IR)
* 5220 MHz [44] (20.0 dBm) (no IR)
* 5240 MHz [48] (20.0 dBm) (no IR)
* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 396 sec)
DFS CAC time: 60000 ms
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* join_ibss
* remain_on_channel
* set_tx_bitrate_mask
* frame
* set_channel
* connect
* disconnect
Supported TX frame types:
* managed: 0x50 0xd0
* AP: 0x50 0xd0
* P2P-client: 0x50 0xd0
* P2P-GO: 0x50 0xd0
Supported RX frame types:
* managed: 0x40 0xd0
* AP: 0x40 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x40 0xd0
WoWLAN support:
* wake up on magic packet
* wake up on pattern match, up to 10 patterns of 1-20 bytes,
maximum packet offset 100 bytes
software interface modes (can always be added):
valid interface combinations:
* #{ managed, P2P-client, P2P-GO } <= 2, #{ AP } <= 1,
total <= 3, #channels <= 1, STA/AP BI must match
Device supports HT-IBSS.
Device has client inactivity timer.
Device supports low priority scan.
Device supports scan flush.
Userspace should do OBSS scan and generate 20/40 coex reports
Coalesce support:
* Maximum 8 coalesce rules supported
* Each rule contains upto 4 patterns of 1-20 bytes,
maximum packet offset 100 bytes
* Maximum supported coalescing delay 100 msecs
Wiphy phy0
max # scan SSIDs: 10
max scan IEs length: 256 bytes
Fragmentation threshold: 2346
RTS threshold: 2347
Retry short limit: 9
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* P2P-client
* P2P-GO
Band 1:
Capabilities: 0x37e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 3-streams
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15, 32
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps
* 5.5 Mbps
* 11.0 Mbps
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (20.0 dBm) (no IR)
Band 2:
Capabilities: 0x37e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 3-streams
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15, 32
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5040 MHz [8] (disabled)
* 5060 MHz [12] (disabled)
* 5080 MHz [16] (disabled)
* 5170 MHz [34] (disabled)
* 5190 MHz [38] (20.0 dBm) (no IR)
* 5210 MHz [42] (20.0 dBm) (no IR)
* 5230 MHz [46] (20.0 dBm) (no IR)
* 5180 MHz [36] (20.0 dBm) (no IR)
* 5200 MHz [40] (20.0 dBm) (no IR)
* 5220 MHz [44] (20.0 dBm) (no IR)
* 5240 MHz [48] (20.0 dBm) (no IR)
* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
DFS state: usable (for 5423 sec)
DFS CAC time: 60000 ms
* 5745 MHz [149] (disabled)
* 5765 MHz [153] (disabled)
* 5785 MHz [157] (disabled)
* 5805 MHz [161] (disabled)
* 5825 MHz [165] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* join_ibss
* remain_on_channel
* set_tx_bitrate_mask
* frame
* set_channel
* connect
* disconnect
Supported TX frame types:
* managed: 0x50 0xd0
* AP: 0x50 0xd0
* P2P-client: 0x50 0xd0
* P2P-GO: 0x50 0xd0
Supported RX frame types:
* managed: 0x40 0xd0
* AP: 0x40 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x40 0xd0
WoWLAN support:
* wake up on magic packet
* wake up on pattern match, up to 10 patterns of 1-20 bytes,
maximum packet offset 100 bytes
software interface modes (can always be added):
valid interface combinations:
* #{ managed, P2P-client, P2P-GO } <= 2, #{ AP } <= 1,
total <= 3, #channels <= 1, STA/AP BI must match
Device supports HT-IBSS.
Device has client inactivity timer.
Device supports low priority scan.
Device supports scan flush.
Userspace should do OBSS scan and generate 20/40 coex reports
Coalesce support:
* Maximum 8 coalesce rules supported
* Each rule contains upto 4 patterns of 1-20 bytes,
maximum packet offset 100 bytes
* Maximum supported coalescing delay 100 msecs***didnt notice any difference
iw mlan0 info
Interface mlan0
ifindex 2
wdev 0x1
addr 28:17:78:35:90:55
ssid Odie
type managed
wiphy 0
Interface mlan0
ifindex 2
wdev 0x1
addr 28:17:78:35:90:55
ssid Odie
type managed
wiphy 0***identical
dmesg
------------[ cut here ]------------
[ 5323.808289] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x259/0x270()
[ 5323.808297] NETDEV WATCHDOG: mlan0 (usb): transmit queue 1 timed out
[ 5323.808302] Modules linked in: ecb btusb bluetooth nls_iso8859_1 nls_cp437 fuse hid_sensor_gyro_3d hid_sensor_incl_3d hid_sensor_rotation hid_sensor_accel_3d hid_sensor_als hid_sensor_magn_3d mwifiex_usb hid_sensor_trigger mwifiex hid_sensor_iio_common industrialio_triggered_buffer kfifo_buf industrialio cfg80211 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common rfkill videodev joydev mousedev media tpm_infineon iTCO_wdt iTCO_vendor_support mac_hid evdev coretemp hwmon intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm rtc_efi pcspkr i915 thermal processor drm_kms_helper snd_hda_codec_hdmi mei_me mei i2c_i801 ac snd_hda_codec_realtek snd_hda_codec_generic lpc_ich tpm_tis video snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
[ 5323.808412] drm tpm intel_gtt i2c_algo_bit button i2c_core battery vboxdrv(O) algif_skcipher af_alg hid_multitouch hid_sensor_hub hid_generic usbhid hid uas usb_storage dm_crypt dm_mod sd_mod crc_t10dif crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel ahci libahci aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ehci_pci libata xhci_hcd ehci_hcd scsi_mod usbcore usb_common tun vfat fat ext4 crc16 mbcache jbd2 ntfs serio
[ 5323.808504] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G O 3.17.2-1-ARCH #1
[ 5323.808512] Hardware name: Microsoft Corporation Surface with Windows 8 Pro/Surface with Windows 8 Pro, BIOS 1.06.0350 04/30/2014
[ 5323.808519] 0000000000000000 be752aa5b8dd5381 ffff88011f303d90 ffffffff815367d0
[ 5323.808528] ffff88011f303dd8 ffff88011f303dc8 ffffffff8107054d 0000000000000001
[ 5323.808536] ffff8800d834cc40 0000000000000002 ffff8801189cc000 0000000000000004
[ 5323.808545] Call Trace:
[ 5323.808551] <IRQ> [<ffffffff815367d0>] dump_stack+0x4d/0x6f
[ 5323.808575] [<ffffffff8107054d>] warn_slowpath_common+0x7d/0xa0
[ 5323.808586] [<ffffffff810705cc>] warn_slowpath_fmt+0x5c/0x80
[ 5323.808610] [<ffffffff81465dd9>] dev_watchdog+0x259/0x270
[ 5323.808622] [<ffffffff81465b80>] ? dev_graft_qdisc+0x80/0x80
[ 5323.808634] [<ffffffff810d5aa6>] call_timer_fn+0x36/0x160
[ 5323.808644] [<ffffffff81465b80>] ? dev_graft_qdisc+0x80/0x80
[ 5323.808656] [<ffffffff810d64d4>] run_timer_softirq+0x274/0x320
[ 5323.808670] [<ffffffff81074402>] __do_softirq+0xf2/0x2e0
[ 5323.808683] [<ffffffff81074746>] irq_exit+0x86/0xb0
[ 5323.808696] [<ffffffff8153f334>] smp_apic_timer_interrupt+0x44/0x50
[ 5323.808709] [<ffffffff8153d5cd>] apic_timer_interrupt+0x6d/0x80
[ 5323.808718] <EOI> [<ffffffff813f27f5>] ? cpuidle_enter_state+0x65/0x1a0
[ 5323.808735] [<ffffffff813f2a17>] cpuidle_enter+0x17/0x20
[ 5323.808749] [<ffffffff810afd1c>] cpu_startup_entry+0x3dc/0x430
[ 5323.808763] [<ffffffff810e3cb3>] ? clockevents_register_device+0xe3/0x150
[ 5323.808773] [<ffffffff8104931e>] start_secondary+0x22e/0x2b0
[ 5323.808781] ---[ end trace 5e658eedf27b02eb ]---
[ 5323.808796] usb 3-3: 4296473696 : Tx timeout(#1), bss_type-num = 0-0
[ 5327.487236] usb 3-3: PREP_CMD: FW is in bad state
[ 5327.487249] usb 3-3: failed to get signal information
[ 5327.487314] usb 3-3: PREP_CMD: FW is in bad state
[ 5327.487320] usb 3-3: failed to get signal information
[ 5333.490696] usb 3-3: PREP_CMD: FW is in bad state
[ 5333.490712] usb 3-3: failed to get signal information
[ 5333.490828] usb 3-3: PREP_CMD: FW is in bad state
[ 5333.490835] usb 3-3: failed to get signal information
[ 5333.812913] usb 3-3: 4296476696 : Tx timeout(#2), bss_type-num = 0-0
[ 5336.489523] usb 3-3: PREP_CMD: FW is in bad state
[ 5336.489545] usb 3-3: scan failed: -1Here I see the timeout message. Not sure what it means by the USB signal failures because I am still able to use the USB as far as opening and closing programs. Just no wifi.
Also note, just to eliminate confusion talking about Arch, Windows VM and Windows 8. Here you see Windows 8 (This is the HOST computer not the VM, which is actually Windows 7) The HOST is a Surface Pro running Windows 8.
journalctlThis command is virtually null. It ends after the EFI boot (I have journaling off due to the use of USB SSD) I'll turn in back on when I have more time to play with this and see what kind of output.
Offline