Edge Computing Division Users Forum

I have a fitpc3LP 4GB (D2x2-T40E-WB-FM4U) purchased from Amazon. Came diskless with wifi module (Realtek 8723ae). I added a 120Gb SSD and installed Ubuntu server 13.04 then upgraded to 13.10. Was a minimal Ubuntu install - no extra packages during install.

Configured wifi with wpa_supplicant and interfaces file, disabled ipv6, disabled wireless power mgmt. Added ifplugd for eth0. Added lm-sensors package for temp info. That's about it.

When fitpc3 is connected to eth0 and not wifi - it seems to run fine. Responsive when connected via ssh and runs for days and days. However, when eth0 is unplugged and fitpc3 is connected to wifi, the ssh cli has delays, ping varies from 1ms to 1200ms (usually every 4 ping packets) and after maybe 10 hours the whole system locks - no network, no console, hard reboot is needed. in each case the monitor has gone to sleep and so no error message to see. Happens on both this fitpc3 as well as a fitpc3 Linux Pro with similar Ubuntu install.

I read there were some issues with the 8723ae driver, but sounds like latest driver was included in 13.04.

Some info:
Ping from a pc-based ubuntu server to fitpc3:
david@ubuntu2:/home/david $ ping 192.168.1.210
PING 192.168.1.210 (192.168.1.210) 56(84) bytes of data.
64 bytes from 192.168.1.210: icmp_req=1 ttl=64 time=55.1 ms
64 bytes from 192.168.1.210: icmp_req=2 ttl=64 time=1.17 ms
64 bytes from 192.168.1.210: icmp_req=3 ttl=64 time=1.55 ms
64 bytes from 192.168.1.210: icmp_req=4 ttl=64 time=4.43 ms
64 bytes from 192.168.1.210: icmp_req=5 ttl=64 time=1.49 ms
64 bytes from 192.168.1.210: icmp_req=6 ttl=64 time=5.61 ms
64 bytes from 192.168.1.210: icmp_req=7 ttl=64 time=40.4 ms
64 bytes from 192.168.1.210: icmp_req=8 ttl=64 time=1208 ms
64 bytes from 192.168.1.210: icmp_req=9 ttl=64 time=209 ms
64 bytes from 192.168.1.210: icmp_req=10 ttl=64 time=1.12 ms
64 bytes from 192.168.1.210: icmp_req=11 ttl=64 time=16.5 ms
64 bytes from 192.168.1.210: icmp_req=12 ttl=64 time=1202 ms
64 bytes from 192.168.1.210: icmp_req=13 ttl=64 time=203 ms
64 bytes from 192.168.1.210: icmp_req=14 ttl=64 time=10.0 ms
64 bytes from 192.168.1.210: icmp_req=15 ttl=64 time=4.32 ms
64 bytes from 192.168.1.210: icmp_req=16 ttl=64 time=1199 ms
64 bytes from 192.168.1.210: icmp_req=17 ttl=64 time=193 ms
64 bytes from 192.168.1.210: icmp_req=18 ttl=64 time=7.17 ms
64 bytes from 192.168.1.210: icmp_req=19 ttl=64 time=25.9 ms
64 bytes from 192.168.1.210: icmp_req=20 ttl=64 time=1215 ms
64 bytes from 192.168.1.210: icmp_req=21 ttl=64 time=207 ms
64 bytes from 192.168.1.210: icmp_req=22 ttl=64 time=1.13 ms

sudo lshw -C network (wlan0 results only):
*-network
description: Wireless interface
product: RTL8723AE PCIe Wireless Network Adapter
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:05:00.0
logical name: wlan0
version: 00
serial: 00:0d:f0:ad:6d:4b
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rtl8723ae driverversion=3.11.0-15-generic firmware=N/A ip=192.168.1.210 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn
resources: irq:18 ioport:1000(size=256) memory:c0800000-c0803fff


I am planning to use the fitpc3 as a remote headless device in 10 installations with more to follow if successful. So need the wifi networking to be solid.

Have there been issues with the 8723ae?
Would another wifi module perform better? I have seen postings mentioning different wifi modules in their fitPc.

Suggestions on how to further troubleshoot / address the issue?
There is little in the log files (/var/log) that gives me any clues as to the specific cause for the hang. But I am no expert.

If needed/helpful i could provide a clonezilla image of the disk (~750Mb).


--Update--
I disabled the onboard wifi (wlan0) and plugged-in / enabled a cheap usb wifi (RT8188 chipset). Pings are 5ms max and there is no delay on the ssh cli. Going to see if hangs over the next few days. Interestingly, just after i plugged-in (but hadn't enabled) the usb wifi the system hung. This time the screen was active and showed "Unable to handle kernel paging request at FFFF880248193300" plus a few more lines of messages.
Not clear that the hang was related to the added USB wifi. I rebooted and again added the usb wifi with no issue as mentioned.
-----------


Thanks.
David

Hi David,
We have tested it with LinuxMint 16 with default settings. No system locks where observed during 48 hours test, in our network ping time vary from about 3ms to maximum 200ms.

Please try LinuxMint 16 MATE LiveUSB to verify. May be it's related to network type. On our side will test latest Ubuntu server and inform you about results.

Mint 16 live running. the pings are not as bad, but still see sporadic delay. the boxes are on the same subnet with only 2 switches apart.

david@ubuntu2:~/src/djs/Lab3/DJS Code$ ping 192.168.1.237
PING 192.168.1.237 (192.168.1.237) 56(84) bytes of data.
64 bytes from 192.168.1.237: icmp_req=1 ttl=64 time=122 ms
64 bytes from 192.168.1.237: icmp_req=2 ttl=64 time=1.10 ms
64 bytes from 192.168.1.237: icmp_req=3 ttl=64 time=1.05 ms
64 bytes from 192.168.1.237: icmp_req=4 ttl=64 time=1.04 ms
64 bytes from 192.168.1.237: icmp_req=5 ttl=64 time=16.0 ms
64 bytes from 192.168.1.237: icmp_req=6 ttl=64 time=1.06 ms
64 bytes from 192.168.1.237: icmp_req=7 ttl=64 time=264 ms
64 bytes from 192.168.1.237: icmp_req=8 ttl=64 time=290 ms
64 bytes from 192.168.1.237: icmp_req=9 ttl=64 time=2.89 ms
64 bytes from 192.168.1.237: icmp_req=10 ttl=64 time=2.69 ms
64 bytes from 192.168.1.237: icmp_req=11 ttl=64 time=0.859 ms
64 bytes from 192.168.1.237: icmp_req=12 ttl=64 time=1.03 ms
64 bytes from 192.168.1.237: icmp_req=13 ttl=64 time=1.00 ms
64 bytes from 192.168.1.237: icmp_req=14 ttl=64 time=1.60 ms
64 bytes from 192.168.1.237: icmp_req=15 ttl=64 time=1.90 ms
64 bytes from 192.168.1.237: icmp_req=16 ttl=64 time=1.56 ms
64 bytes from 192.168.1.237: icmp_req=17 ttl=64 time=0.984 ms
64 bytes from 192.168.1.237: icmp_req=18 ttl=64 time=3.53 ms
64 bytes from 192.168.1.237: icmp_req=19 ttl=64 time=1.06 ms
64 bytes from 192.168.1.237: icmp_req=20 ttl=64 time=1.07 ms
64 bytes from 192.168.1.237: icmp_req=21 ttl=64 time=1.03 ms
64 bytes from 192.168.1.237: icmp_req=22 ttl=64 time=1.01 ms
64 bytes from 192.168.1.237: icmp_req=23 ttl=64 time=323 ms
64 bytes from 192.168.1.237: icmp_req=24 ttl=64 time=322 ms
64 bytes from 192.168.1.237: icmp_req=25 ttl=64 time=1.03 ms
64 bytes from 192.168.1.237: icmp_req=26 ttl=64 time=1.05 ms
64 bytes from 192.168.1.237: icmp_req=27 ttl=64 time=320 ms
64 bytes from 192.168.1.237: icmp_req=28 ttl=64 time=333 ms
64 bytes from 192.168.1.237: icmp_req=29 ttl=64 time=1.03 ms
64 bytes from 192.168.1.237: icmp_req=30 ttl=64 time=1.04 ms
64 bytes from 192.168.1.237: icmp_req=31 ttl=64 time=304 ms
64 bytes from 192.168.1.237: icmp_req=32 ttl=64 time=315 ms
64 bytes from 192.168.1.237: icmp_req=33 ttl=64 time=1.06 ms
64 bytes from 192.168.1.237: icmp_req=34 ttl=64 time=1.03 ms
64 bytes from 192.168.1.237: icmp_req=35 ttl=64 time=1.06 ms
64 bytes from 192.168.1.237: icmp_req=36 ttl=64 time=5.81 ms
64 bytes from 192.168.1.237: icmp_req=37 ttl=64 time=4.76 ms
64 bytes from 192.168.1.237: icmp_req=38 ttl=64 time=1.05 ms
64 bytes from 192.168.1.237: icmp_req=39 ttl=64 time=280 ms
64 bytes from 192.168.1.237: icmp_req=40 ttl=64 time=304 ms
64 bytes from 192.168.1.237: icmp_req=41 ttl=64 time=1.01 ms
64 bytes from 192.168.1.237: icmp_req=42 ttl=64 time=1.04 ms
^C
--- 192.168.1.237 ping statistics ---
42 packets transmitted, 42 received, 0% packet loss, time 41041ms
rtt min/avg/max/mdev = 0.859/77.269/333.839/129.544 ms
david@ubuntu2:~/src/djs/Lab3/DJS Code$


I'll let it run for a day or two and see if it locks.

As for running Ubuntu. I installed 13.04 server and upgraded to 13.10 (13.10 install was hanging on the second screen). I then configured wpa_supplicant, interfaces file, ifplugd, disabled ipv6, disabled wireless power mgmt, and installed lm-sensors. That's about it. I am usually logged in via putty ssh connection.

As mentioned, I have a clonezilla image if that would help.

I am no Linux expert. What do you mean by "May be it's related to network type."?

Thanks for looking into this.

As of now, Mint 16 Live is hung. I was SSh'd into the system via putty. I had added openssh-server to the system so I could connect. As of this morning, the ssh connection had dropped and the console is non responsive. Since the screen had blanked due to non activity, I have no info on the crash. However I expect it to be same as previously seen kernel panic on Ubuntu.

We cannot reproduce the system crash. Also we have never seen such behavior. The issue is probably OS SW/driver related, so if you can try to check other WiFi card/chipset.

Some tips:
1. Please verify it is not related to Storage or Memory failures.
2. Please refer to the following thread:
http://www.fit-pc.com/forum/viewtopic.p ... 3ae#p14701
3. You can find RTL8723AE Wi-Fi driver reference:
http://www.fit-pc.com/wiki/index.php/In ... ux_Mint_13
4. Please try a clear installation of Linux Mint 15, our official OS.
http://www.fit-pc.com/wiki/index.php/Fi ... ux_Mint_15