I have a PYNQ-Z2 board and it contains FT2232HQ chip, which convert data from USB to JTAG and UART
The problem is the board is working and is detected by Vivado (I can program it), but the device doesn't show up as /dev/ttyUSB* device, it shows up as /dev/ftdi-x (where x is a random number) and I can't open a serial port with this device file.
I used lsusb command and I found the chip is correctly detected:
Bus 003 Device 017: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
After that I tried to check the syslog file, and I noticed two weird behaviors, the first is when I connect the board two ttyUSB devices are recognized, not one! /dev/ttyUSB0 & /dev/ttyUSB1.
the second behavior is these two devices are immediately disconnected after they are connected.
Here is the full syslog:
Oct 27 11:45:20 ao20xa kernel: [73109.798748] usb 3-4: new high-speed USB device number 17 using xhci_hcd
Oct 27 11:45:21 ao20xa kernel: [73109.949757] usb 3-4: New USB device found, idVendor=0403, idProduct=6010
Oct 27 11:45:21 ao20xa kernel: [73109.949761] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 27 11:45:21 ao20xa kernel: [73109.949763] usb 3-4: Product: TUL
Oct 27 11:45:21 ao20xa kernel: [73109.949765] usb 3-4: Manufacturer: Xilinx
Oct 27 11:45:21 ao20xa kernel: [73109.949767] usb 3-4: SerialNumber: 1234-tul
Oct 27 11:45:21 ao20xa kernel: [73109.950844] ftdi_sio 3-4:1.0: FTDI USB Serial Device converter detected
Oct 27 11:45:21 ao20xa kernel: [73109.950899] usb 3-4: Detected FT2232H
Oct 27 11:45:21 ao20xa kernel: [73109.951100] usb 3-4: FTDI USB Serial Device converter now attached to ttyUSB0
Oct 27 11:45:21 ao20xa kernel: [73109.951815] ftdi_sio 3-4:1.1: FTDI USB Serial Device converter detected
Oct 27 11:45:21 ao20xa kernel: [73109.951861] usb 3-4: Detected FT2232H
Oct 27 11:45:21 ao20xa kernel: [73109.952058] usb 3-4: FTDI USB Serial Device converter now attached to ttyUSB1
Oct 27 11:45:21 ao20xa mtp-probe: checking bus 3, device 17: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
Oct 27 11:45:21 ao20xa mtp-probe: bus: 3, device: 17 was not an MTP device
Oct 27 11:45:21 ao20xa systemd-udevd[18701]: Process '/bin/sh -c 'basename $(dirname $(realpath /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/device)) > /sys/bus/usb/drivers/ftdi_sio/unbind'' failed with exit code 1.
Oct 27 11:45:21 ao20xa kernel: [73110.089464] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
Oct 27 11:45:21 ao20xa kernel: [73110.089536] ftdi_sio 3-4:1.1: device disconnected
Oct 27 11:45:21 ao20xa kernel: [73110.089818] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Oct 27 11:45:21 ao20xa kernel: [73110.089865] ftdi_sio 3-4:1.0: device disconnected
Oct 27 11:45:21 ao20xa snapd[16139]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0
Oct 27 11:45:21 ao20xa snapd[16139]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1
Oct 27 11:45:21 ao20xa systemd-udevd[18701]: Process '/bin/sh -c 'basename $(dirname $(realpath /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/device)) > /sys/bus/usb/drivers/ftdi_sio/unbind'' failed with exit code 1.
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4
Oct 27 11:45:21 ao20xa ModemManager[1044]: <info> (tty/ttyUSB0): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4'
Oct 27 11:45:21 ao20xa ModemManager[1044]: <info> (tty/ttyUSB1): released by device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4'
Oct 27 11:45:21 ao20xa ModemManager[1044]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4': Operation was cancelled
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0
Oct 27 11:45:21 ao20xa upowerd[1835]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.1
So, I wonder if any one could help fixing this problem.
In my case, my user wasn't in the group dialout. When I added:
sudo adduser <my_user> dialout
And logged out and in, finally after the hours of looking for the answer I managed to connect to the serial.
As mentioned in the comments by Ian Abbot and Abady, running:
grep -l ftdi_sio /etc/udev/rules.d/*.rules
and commenting out the lines there helped. For me they were:
#lattice
#BUS=="usb", ACTION=="add", ATTRS{idVendor}=="1134", ATTRS{idProduct}=="8001", MODE=="0666", GROUP=="plugdev", SYMLINK+="lattice-%n"
#FTDI
#SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE=="0666", GROUP=="plugdev", SYMLINK+="ftdi-%n"
#SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", RUN+="/bin/sh -c 'basename %p >/sys/bus/usb/drivers/ftdi_sio/unbind'"
It seems there was a rule which was causing the disconnect (renaming the ttyUSB* to ftdi-*)
Related
Question (TL;DR):
For an SDcard with multiple partitions, how to get at least "change" event for the mounted nodes from udev, when an uSD or SDcard is removed from USB-SD reader, without disconnecting USB cable from your PC?
Bonus: Get "add/remove" event for "partition" nodes ( e.g "/dev/sdh2" )
What does not work:
When a partition is mounted, udev does not output any event for the partition node, when the card is removed !!!
Steps to reproduce:
You need a USB-SD reader ( I highly recommend: https://www.kingston.com/en/flash/readers/FCR-HS4 ). But I tested on many other USB-SD readers (Such as GenesysLogic based ones), situation is the same.
You need an uSD or SDcard , with at least 1 or 2 partition.
Step1:
Create a new udev rule, named as: /etc/udev/rules.d/98-test.rules
Content:
KERNEL!="sd*" , SUBSYSTEM!="block", GOTO="END"
LABEL="WORK"
ACTION=="add", RUN+="/usr/bin/logger *****Received add event for %k*****"
ACTION=="remove", RUN+="/usr/bin/logger *****Received remove event for %k*****"
ACTION=="change", RUN+="/usr/bin/logger *****Received change event for %k*****"
LABEL="END"
Step2:
Install ccze ( sudo apt install ccze ). This will give you beautiful colored logging for events.
Open a terminal, run following command:
journalctl -f | ccze -A
Result:
Mar 09 23:01:32 Ev-Turbo kernel: sd 6:0:0:3: [sdh] 30408704 512-byte logical blocks: (15.6 GB/14.5 GiB)
Mar 09 23:01:32 Ev-Turbo kernel: sdh: sdh1 sdh2
Mar 09 23:01:33 Ev-Turbo root[19519]: *****Received change event for sdh*****
Mar 09 23:01:33 Ev-Turbo root[19523]: *****Received change event for sdh*****
Mar 09 23:01:33 Ev-Turbo root[19545]: *****Received add event for sdh2*****
Mar 09 23:01:33 Ev-Turbo root[19552]: *****Received add event for sdh1*****
Step3:
Now remove the uSD card from the slot, but don't disconnect USB cable from your PC. Watch the log:
Mar 09 23:06:56 Ev-Turbo root[21220]: *****Received change event for sdh*****
Mar 09 23:06:56 Ev-Turbo root[21223]: *****Received remove event for sdh2*****
Mar 09 23:06:56 Ev-Turbo root[21222]: *****Received remove event for sdh1*****
Step4:
Now, insert your uSD card again, you will see:
Mar 09 23:11:21 Ev-Turbo kernel: sd 6:0:0:3: [sdh] 30408704 512-byte logical blocks: (15.6 GB/14.5 GiB)
Mar 09 23:11:21 Ev-Turbo kernel: sdh: sdh1 sdh2
Mar 09 23:11:21 Ev-Turbo root[22652]: *****Received change event for sdh*****
Mar 09 23:11:21 Ev-Turbo root[22653]: *****Received change event for sdh*****
Mar 09 23:11:21 Ev-Turbo root[22679]: *****Received add event for sdh2*****
Mar 09 23:11:21 Ev-Turbo root[22682]: *****Received add event for sdh1*****
And now, try mount one of the partitions to somewhere in your system:
sudo mount /dev/sdh2 /media/uSD2
You can double check if it is really mounted ( run commands: lsblk, mount...etc)
Step5:
Now, while the partition is mounted, remove your uSD card from the slot. Watch the log:
Mar 09 23:12:32 Ev-Turbo root[23049]: *****Received change event for sdh*****
Nothing more... Why there is no "remove" event anymore???
BONUS NOTES (Irrelevant to above question):
1) Most of the info on the web regarding udev/systemd/systemd-udevd and mount scripts are obsolete. Especially, for systemd v239, many of the "solved/working" answers are not usable ( Working on the issue for 2 weeks, read most of the solutions on the web, Tested on Debian 9.7, Linux Mint 18.3, Ubuntu 18.04 )
2) For systemd versions > 212, you need service files to mount your removable devices. Example:
https://serverfault.com/questions/766506/automount-usb-drives-with-systemd
3) Especially for systemd v239, you need to disable PrivateMounts to achieve automatic mounting via systemd units. For details: https://unix.stackexchange.com/questions/464959/udev-rule-to-automount-media-devices-stopped-working-after-systemd-was-updated-t
4) Mount unit files does not fit for every case, for example, when you want to mount to some specific directories based on USB host, port,lun numbers... But for some cases, this approach is very easy: https://dev.to/adarshkkumar/mount-a-volume-using-systemd-1h2f
I've been fighting with this for a few days now. Whenever I run a watchKit App from the simulator my mac will get the black screen of death and reboot my machine. I am running XCode 8.2.1 running simulators for iPhone 6 or 7 and watches with watchOS 3 for both the original watch and version 2 in both sizes. The watch simulator will start, but whenever it attempts to launch a watchkit app that was deployed with XCode my machine will crash. This can be any watchkit app, even a simple Hello World app.
I have also tried completely uninstalling XCode 8 and 7 as well as all of the simulators and derived info, but the watch apps will still crash my machine. I've filed a bug report with Apple, but they won't reply back to me. I am also running on a Mid 2014 MacBook Pro with Sierra version 10.12.3.
Has anyone else experienced this? I'm running out of ideas to fix this and I cannot do anything watch related until I get past this. I've listed some of the logs from the activity monitor below as well as the Panic report:
ACTIVITY LOG:
Mar 24 09:04:17 C02N618RG3QD logd[74]: _purge_uuidtext unlinking /var/db/uuidtext/FD/2940F9BA8137988BB56CC86EFEDC84
Mar 24 09:04:17 C02N618RG3QD logd[74]: _purge_uuidtext unlinking /var/db/uuidtext/FE/872728C5713EA69D9D3FBC6C653C19
Mar 24 09:04:17 C02N618RG3QD logd[74]: _purge_uuidtext unlinking /var/db/uuidtext/FE/B838E71BA739F4AA6F121E88E788B5
Mar 24 09:04:17 C02N618RG3QD logd[74]: _purge_uuidtext unlinking /var/db/uuidtext/FF/0B49D70BCF30419AD992D76F372F19
Mar 24 09:04:17 C02N618RG3QD logd[74]: _purge_uuidtext total: 3188, in_use:2294, marked:0, recent:254, deleted 640
Mar 24 09:04:17 C02N618RG3QD logd[74]: _purge_uuidtext slib tree cleaned up (0)
Mar 24 09:04:17 C02N618RG3QD logd[74]: _purge_uuidtext uuid tree cleaned up (3)
Mar 24 09:04:17 C02N618RG3QD logd[74]: _purge_uuidtext cleaned up (0)
Mar 24 09:04:17 C02N618RG3QD logd[74]: Purged 114692767 bytes from uuidtext.
Mar 24 09:04:18 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe03260b130>: 9223372036854847488.000000]
Mar 24 09:04:18 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe034800ba0>: 9223372036854855680.000000]
Mar 24 09:04:18 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe03260ac80>: 9223372036854855680.000000]
Mar 24 09:04:18 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe0349017f0>: 9223372036854855680.000000]
Mar 24 09:04:18 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe034a07340>: 9223372036854855680.000000]
Mar 24 09:04:18 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe0324107b0>: 9223372036854855680.000000]
Mar 24 09:04:18 C02N618RG3QD useractivityd[1022]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked
Mar 24 09:04:19 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe034b0e0c0>: 9223372036854855680.000000]
Mar 24 09:04:19 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe0326088d0>: 9223372036854855680.000000]
Mar 24 09:04:19 C02N618RG3QD UserEventAgent[1178]: assertion failed: 16D32 14S471a: com.apple.cts + 20609 [D0046D83-09B7-3C10-A783-396F29B9B380]: 0x0
Mar 24 09:04:21 C02N618RG3QD com.apple.xpc.launchd[1] (com.mcafee.ssm.ScanManager): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Mar 24 09:04:22 C02N618RG3QD com.apple.xpc.launchd[1] (com.apple.nowplayingtouchui): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Mar 24 09:04:22 C02N618RG3QD com.apple.xpc.launchd[1] (com.apple.quicklook[30456]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
Mar 24 09:04:32 C02N618RG3QD com.apple.xpc.launchd[1] (com.mcafee.ssm.ScanManager): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Mar 24 09:04:33 C02N618RG3QD com.apple.xpc.launchd[1] (com.apple.nowplayingtouchui): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Mar 24 09:04:39 C02N618RG3QD IBCocoaTouchImageCatalogTool[30517]: assertion failed: 16D32: libxpc.dylib + 34617 [D3538D2B-EEA9-3C74-890E-6F4AE4F51F0E]: 0x8d
Mar 24 09:04:40 C02N618RG3QD IBCocoaTouchImageCatalogTool[30517]: BUG in libdispatch client: kevent[EVFILT_VNODE] add: "Bad file descriptor" - 0x9
Mar 24 09:04:42 C02N618RG3QD Interface Builder WatchKit Tool[30530]: assertion failed: 16D32: libxpc.dylib + 34617 [D3538D2B-EEA9-3C74-890E-6F4AE4F51F0E]: 0x8d
Mar 24 09:04:42 --- last message repeated 2 times ---
Mar 24 09:04:42 C02N618RG3QD Interface Builder WatchKit Tool[30530]: BUG in libdispatch client: kevent[EVFILT_VNODE] add: "Bad file descriptor" - 0x9
Mar 24 09:04:42 C02N618RG3QD com.apple.xpc.launchd[1] (com.mcafee.ssm.ScanManager): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Mar 24 09:04:43 C02N618RG3QD com.apple.xpc.launchd[1] (com.apple.nowplayingtouchui): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30670]: assertion failed: 16D32 14C89: libxpc.dylib + 31485 [0339A402-6531-30E9-8BC2-589C463CD6D6]: 0x8d
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30671]: assertion failed: 16D32 14C89: libxpc.dylib + 31485 [0339A402-6531-30E9-8BC2-589C463CD6D6]: 0x8d
Mar 24 09:04:47 --- last message repeated 1 time ---
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30670]: assertion failed: 16D32 14C89: libxpc.dylib + 31485 [0339A402-6531-30E9-8BC2-589C463CD6D6]: 0x8d
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30671]: BUG in libdispatch: 16D32 14C89 - 1296 - 0x2
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30670]: BUG in libdispatch: 16D32 14C89 - 1296 - 0x2
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30671]: BUG in libdispatch client: kevent[EVFILT_VNODE] add: "Bad file descriptor" - 0x9
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30670]: BUG in libdispatch client: kevent[EVFILT_VNODE] add: "Bad file descriptor" - 0x9
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30671]: assertion failed: 16D32 14C89: libxpc.dylib + 31485 [0339A402-6531-30E9-8BC2-589C463CD6D6]: 0x8d
Mar 24 09:04:47 C02N618RG3QD Interface Builder Cocoa Touch Tool[30670]: assertion failed: 16D32 14C89: libxpc.dylib + 31485 [0339A402-6531-30E9-8BC2-589C463CD6D6]: 0x8d
Mar 24 09:04:48 C02N618RG3QD IBCocoaTouchImageCatalogTool[30687]: BUG in libdispatch: 16D32 14C89 - 1296 - 0x2
Mar 24 09:04:48 C02N618RG3QD IBCocoaTouchImageCatalogTool[30687]: BUG in libdispatch client: kevent[EVFILT_VNODE] add: "Bad file descriptor" - 0x9
Mar 24 09:04:52 C02N618RG3QD com.apple.xpc.launchd[1] (com.mcafee.ssm.ScanManager): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Mar 24 09:04:53 C02N618RG3QD com.apple.xpc.launchd[1] (com.apple.nowplayingtouchui): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Mar 24 09:04:58 C02N618RG3QD Simulator (Watch)[30853]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked
Mar 24 09:05:00 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe032706fc0>: 9223372036854857728.000000]
Mar 24 09:05:00 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe0327081f0>: 9223372036854857728.000000]
Mar 24 09:05:00 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe0326114b0>: 9223372036854857728.000000]
Mar 24 09:05:00 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe03250fbf0>: 9223372036854857728.000000]
Mar 24 09:05:00 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe03250d9d0>: 9223372036854857728.000000]
AND
Mar 24 09:05:53 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe034801f40>: 9223372036854861824.000000]
Mar 24 09:05:53 C02N618RG3QD diagnosticd[380]: JSON->NS failed [type" : "u",
"timestamp" : 58798649826108
},
"timeGMTsec" : 1490360753,
"procid" : {
"procid" : 30972,
"_type" : "u"
},
"persisted" : {
"_type" : "b",
"persisted" : 0
},
"thread" : {
"_type" : "u",
"thread" : 529028
},
"pid" : {
"pid" : 30972,
"_type" : "u"
},
"procpath" : "\/Applications\/Xcode.app\/Contents\/Developer\/Platforms\/iPhoneSimulator.platform\/Developer\/SDKs\/iPhoneSimulator.sdk\/System\/Library\/CoreServices\/SpringBoard.app\/SpringBoard",
"SIMULATOR_UDID" : "4855B6A5-7A82-49AE-94E4-DBA2BED65585"
}]
Mar 24 09:05:53 C02N618RG3QD diagnosticd[380]: Unexpected xpc type [<double: 0x7fe032403a30>: 9223372036854861824.000000]
PANIC REPORT
Anonymous UUID: 56E742E7-D1F7-AB9B-90CC-58BFFAFB991E
Fri Mar 24 09:07:31 2017
*** Panic Report ***
panic(cpu 4 caller 0xffffff8018e05ecd): Kernel trap at 0xffffff8018dfc620, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff806783403c, CR3: 0x00000002cb9b6256, CR4: 0x00000000001627e0
RAX: 0x00000000ffffff01, RBX: 0x000000002d1e202c, RCX: 0x00000000ffffffa1, RDX: 0x000000000000000a
RSP: 0xffffff921b9fb7c0, RBP: 0xffffff921b9fb7c0, RSI: 0xffffff7f9c364723, RDI: 0xffffff806783403c
R8: 0x0000000000000002, R9: 0x0000000000000ff8, R10: 0xe326417ed3850092, R11: 0xffffff804d3b5bb8
R12: 0x000000000000000a, R13: 0x0000000000000054, R14: 0x0000000000906065, R15: 0xffffff803a652010
RFL: 0x0000000000010206, RIP: 0xffffff8018dfc620, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff806783403c, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 1
Backtrace (CPU 4), Frame : Return Address
0xffffff921b9fb450 : 0xffffff8018cf210c
0xffffff921b9fb4d0 : 0xffffff8018e05ecd
0xffffff921b9fb6b0 : 0xffffff8018ca3743
0xffffff921b9fb6d0 : 0xffffff8018dfc620
0xffffff921b9fb7c0 : 0xffffff7f9c33e471
0xffffff921b9fb800 : 0xffffff7f9c33e4fa
0xffffff921b9fb830 : 0xffffff7f9c33e719
0xffffff921b9fb910 : 0xffffff7f9c33e839
0xffffff921b9fb950 : 0xffffff7f9c3604fa
0xffffff921b9fb9a0 : 0xffffff7f9c3603b4
0xffffff921b9fb9c0 : 0xffffff7f9c3474b7
0xffffff921b9fbe60 : 0xffffff7f9c3479e1
0xffffff921b9fbf40 : 0xffffff8202aea6a0
0xffffff921b9fbf50 : 0xffffff8019227066
0xffffff921b9fbfb0 : 0xffffff8018ca3c38
Kernel Extensions in backtrace:
com.verdasys.dgagent(23.20.7)[90F4996A-8100-3509-BBCA-9778AAA30E30]#0xffffff7f9c338000->0xffffff7f9c374fff
dependency: com.apple.security.sandbox(300.0)[8997F7FD-7C04-38F6-86DB-BACDE9137374]#0xffffff7f99937000
BSD process name corresponding to current thread: xpcproxy_sim
Mac OS version:
16D32
Kernel version:
Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64
Kernel UUID: C67A8D03-DEAC-35B8-8F68-06FF7B687215
Kernel slide: 0x0000000018a00000
Kernel text base: 0xffffff8018c00000
__HIB text base: 0xffffff8018b00000
System model name: MacBookPro11,3 (Mac-2BD1B31983FE1663)
System uptime in nanoseconds: 2958365287234
last loaded kext at 359084323236: com.apple.filesystems.smbfs 3.1.1 (addr 0xffffff7f998b3000, size 425984)
loaded kexts:
com.McAfee.FMPSysCore 1
com.verdasys.dgagent 0023.20.7
com.intel.kext.intelhaxm 1.1.1
com.squirrels.airparrot.framebuffer 5
com.squirrels.driver.AirParrotSpeakers 1.8
com.apple.filesystems.smbfs 3.1.1
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.driver.AGPM 110.23.14
com.apple.driver.ApplePlatformEnabler 2.7.0d0
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.pmtelemetry 1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.iokit.IOBluetoothSerialManager 5.0.3f1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHV 1
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleGraphicsDevicePolicy 3.13.79
com.apple.driver.AppleHDAHardwareConfigDriver 278.56
com.apple.driver.AppleHDA 278.56
com.apple.driver.AppleUpstreamUserClient 3.6.4
com.apple.GeForce 10.1.4
com.apple.driver.AppleIntelHD5000Graphics 10.2.2
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.AppleBacklight 170.9.10
com.apple.driver.AppleLPC 3.1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 5.0.3f1
com.apple.nvidia.NVDAStartup 10.1.4
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AppleSMCLMU 208
com.apple.driver.AppleCameraInterface 5.57.0
com.apple.driver.AppleMuxControl 3.13.79
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.AppleIntelFramebufferAzul 10.2.2
com.apple.driver.AppleThunderboltIP 3.0.8
com.apple.driver.AppleMCCSControl 1.2.15
com.apple.driver.AppleUSBDisplays 380
com.apple.iokit.SCSITaskUserClient 394.30.2
com.apple.driver.AppleUSBStorageCoexistentDriver 404.30.1
com.apple.driver.AppleUSBCardReader 404.30.1
com.apple.iokit.IOBluetoothUSBDFU 5.0.3f1
com.apple.driver.AppleUSBTCKeyEventDriver 252
com.apple.driver.AppleUSBTCKeyboard 252
com.apple.driver.AppleUSBTCButtons 252
com.apple.driver.CoreStorageFsck 540.30.1
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.BootCache 40
com.apple.filesystems.hfs.kext 366.30.3
com.apple.iokit.IOAHCIBlockStorage 295.20.1
com.apple.driver.AppleAHCIPort 326
com.apple.iokit.AppleBCM5701Ethernet 10.2.7
com.apple.driver.AppleFWOHCI 5.5.5
com.apple.driver.AirPort.Brcm4360 1130.3.1a5
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 5.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 5.0
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 172
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 11
com.apple.driver.AppleSSE 1.0
com.apple.driver.DspFuncLib 278.56
com.apple.kext.OSvKernDSPLib 525
com.apple.nvidia.driver.NVDAGK100Hal 10.1.4
com.apple.nvidia.driver.NVDAResman 10.1.4
com.apple.iokit.IOSurface 153.3
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.iokit.IOFireWireIP 2.2.7
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.IOPlatformPluginFamily 6.0.0d8
com.apple.iokit.IOBluetoothHostControllerUSBTransport 5.0.3f1
com.apple.iokit.IOBluetoothHostControllerTransport 5.0.3f1
com.apple.iokit.IOBluetoothFamily 5.0.3f1
com.apple.driver.AppleHDAController 278.56
com.apple.iokit.IOHDAFamily 278.56
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 513.1
com.apple.driver.AppleGraphicsControl 3.13.79
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.AppleGraphicsDeviceControl 3.13.79
com.apple.iokit.IOAcceleratorFamily2 289.32
com.apple.driver.AppleThunderboltEDMSink 4.1.1
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.AppleSMBusController 1.0.14d1
com.apple.iokit.IOGraphicsFamily 513.1
com.apple.driver.AppleUSBComposite 900.4.1
com.apple.driver.AppleUSBAudio 307.7
com.apple.iokit.IOAudioFamily 205.12
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IOUSBMassStorageClass 4.0.4
com.apple.iokit.IOSCSIBlockCommandsDevice 394.30.2
com.apple.iokit.IOUSBMassStorageDriver 131.1.1
com.apple.iokit.IOSCSIArchitectureModelFamily 394.30.2
com.apple.driver.AppleThunderboltDPInAdapter 4.6.1
com.apple.driver.AppleThunderboltDPOutAdapter 4.6.1
com.apple.driver.AppleThunderboltDPAdapterFamily 4.6.1
com.apple.driver.AppleThunderboltPCIUpAdapter 2.1.1
com.apple.driver.AppleThunderboltPCIDownAdapter 2.1.1
com.apple.driver.AppleUSBMultitouch 258
com.apple.driver.usb.IOUSBHostHIDDevice 1.1
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.1
com.apple.driver.CoreStorage 540.30.1
com.apple.filesystems.hfs.encodings.kext 1
com.apple.driver.AppleUSBMergeNub 900.4.1
com.apple.driver.usb.AppleUSBHub 1.1
com.apple.driver.AppleXsanScheme 3
com.apple.iokit.IOAHCIFamily 288
com.apple.driver.usb.AppleUSBEHCIPCI 1.1
com.apple.driver.usb.AppleUSBEHCI 1.1
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.iokit.IOFireWireFamily 4.6.5
com.apple.driver.AppleThunderboltNHI 4.1.8
com.apple.iokit.IOThunderboltFamily 6.3.3
com.apple.iokit.IO80211Family 1200.12.2
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.driver.corecapture 1.0.4
com.apple.driver.AppleIntelLpssGspi 3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI 1.1
com.apple.driver.usb.AppleUSBXHCI 1.1
com.apple.driver.usb.AppleUSBHostPacketFilter 1.0
com.apple.iokit.IOUSBFamily 900.4.1
com.apple.driver.AppleUSBHostMergeProperties 1.1
com.apple.driver.AppleEFINVRAM 2.1
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.KernelRelayHost 1
com.apple.iokit.IOUSBHostFamily 1.1
com.apple.driver.AppleBusPowerController 1.0
com.apple.driver.DiskImages 444.41.1
com.apple.iokit.IOStorageFamily 2.1
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 5.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.Libm 1
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
You have Verdasys Digital Guardian Agent and McAfee installed, both of which have injected kernel extensions that may be causing the panic.
It appears to be happening during an XPC call's security checks. The Simulator is a separate user space sharing the host Mac kernel. My guess is the developers of one or both kernel extensions are not properly handling certain data or are mangling private kernel data structures. $rip is the address of the next instruction. Page faulting on that address means something has gone seriously wrong.
I suggest uninstalling all 3rd-party kernel extensions then attempting to reproduce the problem. If that fixes it then file a bug with Verdasys or McAfee to have them fix their kernel extensions.
Apparently there is a known problem of XFS locking up the kernel/processes and corrupting volumes under heavy traffic.
Some web pages talk about it, but I was not able to figure out which pages are new and may have a solution.
My company's deployments have Debian with kernel 3.4.107, xfsprogs 3.1.4, and large storage arrays.
We have large data (PB) and high throughput (GB/sec) using async IO to several large volumes.
We constantly experience these unpredictable lockups on several systems.
Kernel logs/dmesg show something like the following:
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986515] INFO: task Sr2dReceiver-5:46829 blocked for more than 120 seconds.
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986518] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986520] Sr2dReceiver-5 D ffffffff8105b39e 0 46829 7284 0x00000000
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986524] ffff881e71f57b38 0000000000000082 000000000000000b ffff884066763180
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986529] 0000000000000000 ffff884066763180 0000000000011180 0000000000011180
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986532] ffff881e71f57fd8 ffff881e71f56000 0000000000011180 ffff881e71f56000
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986536] Call Trace:
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986545] [<ffffffff814ffe9f>] schedule+0x64/0x66
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986548] [<ffffffff815005f3>] rwsem_down_failed_common+0xdb/0x10d
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986551] [<ffffffff81500638>] rwsem_down_write_failed+0x13/0x15
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986555] [<ffffffff8126b583>] call_rwsem_down_write_failed+0x13/0x20
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986558] [<ffffffff814ff320>] ? down_write+0x25/0x27
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986572] [<ffffffffa01f29e0>] xfs_ilock+0xbc/0x12e [xfs]
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986580] [<ffffffffa01eec71>] xfs_rw_ilock+0x2c/0x33 [xfs]
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986586] [<ffffffffa01eec71>] ? xfs_rw_ilock+0x2c/0x33 [xfs]
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986593] [<ffffffffa01ef234>] xfs_file_aio_write_checks+0x41/0xfe [xfs]
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986600] [<ffffffffa01ef358>] xfs_file_buffered_aio_write+0x67/0x179 [xfs]
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986603] [<ffffffff8150099a>] ? _raw_spin_unlock_irqrestore+0x30/0x3d
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986611] [<ffffffffa01ef81d>] xfs_file_aio_write+0x163/0x1b5 [xfs]
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986614] [<ffffffff8106f1af>] ? futex_wait+0x22c/0x244
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986619] [<ffffffff8110038e>] do_sync_write+0xd9/0x116
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986622] [<ffffffff8150095f>] ? _raw_spin_unlock+0x26/0x31
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986634] [<ffffffff8106f2f1>] ? futex_wake+0xe8/0xfa
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986637] [<ffffffff81100d1d>] vfs_write+0xae/0x10a
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986639] [<ffffffff811015b3>] ? fget_light+0xb0/0xbf
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986642] [<ffffffff81100dd3>] sys_pwrite64+0x5a/0x79
2016 Mar 24 04:42:34 hmtmzhbgb01-ssu-1 kernel: [2358750.986645] [<ffffffff81506912>] system_call_fastpath+0x16/0x1b
Lockups leave the system in a bad state. The processes in D state that hang cannot even be killed with signal 9.
The only way to resume operations is to reboot, repair XFS and then the system works for another while.
But occasionally after the lockup we cannot even repair some volumes, as they get totally corrupted and we need to rebuild them with mkfs.
As a last resort, we now run xfs-repair periodically and this reduced the frequency of lockups and data loss to a certain extent.
But the incidents still occur often enough, so we need some solution.
I was wondering if there is a solution for this with kernel 3.4.107, e.g. some patch that we may apply.
Due to the large number of deployments and other software issues, we cannot upgrade the kernel in the near future.
However, we are working towards updating our applications so that we can run on kernel 3.16 in our next releases.
Does anyone know if this XFS lockup problem was fixed in 3.16?
Some people have experienced this but it was not a problem with XFS it was because the kernel was unable to flush dirty pages within the 120s time period. Have a look here but please check the numbers they're using as default on your own system.
http://blog.ronnyegner-consulting.de/2011/10/13/info-task-blocked-for-more-than-120-seconds/
and here
http://www.blackmoreops.com/2014/09/22/linux-kernel-panic-issue-fix-hung_task_timeout_secs-blocked-120-seconds-problem/
You can see what you're dirty cache ratio is by running this
sysctl -a | grep dirty
or
cat /proc/sys/vm/dirty_ratio
The best write up on this I could find is here...
https://lonesysadmin.net/2013/12/22/better-linux-disk-caching-performance-vm-dirty_ratio/
Essentially you need to tune your application to make sure that it can write the dirty buffers to disk within the time period or change the timer period etc.
You can also see some interesting paramaters as follows
sysctl -a | grep hung
You could increase the timeout permanently using /etc/sysctl.conf as follows...
kernel.hung_task_timeout_secs = 300
Does anyone know if this XFS lockup problem was fixed in 3.16?
It is said so in A Short Guide to Kernel Debugging:
Searching for “xfs splice deadlock” turns up an email thread from 2011 that describes this
problem. However, bisecting the kernel source repository shows that
the bug wasn’t really addressed until April, 2014 (8d02076) for release in Linux 3.16.
I am using gammu-smsd 1.31.90, I made a udev rule for my USB 3g dongle but gammu-smsd can not connect to device. It says DEVICEOPENERROR[2].
How can I fix it?
udev-rule in /etc/udev/rules.d/10-rules.local
SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", SYMLINK+="phone", GROUP="dialout"
Gammu log:
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: Starting phone communication...
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Gammu 1.31.90 built 08:54:06 May 23 2012 using GCC 4.6]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Connection - "at"]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Connection index - 0]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Model type - ""]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Device - "/dev/phone"]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [Running on - Linux, kernel 3.4.103 (#4 SMP PREEMPT Thu Dec 18 12:55:58 CST 2014)]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: [System error - tcgetattr in serial_open, 25, "Inappropriate ioctl for device"]
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: gammu: Init:GSM_TryGetModel failed with error DEVICEOPENERROR[2]: Error opening device. Unknown, busy or no permissions.
Wed 2016/03/09 15:57:58 gammu-smsd[2466]: Can't open device: Error opening device. Unknown, busy or no permissions. (DEVICEOPENERROR[2])
You Have to config 2 files and edite 'port' and 'Connection' fields.
gammu-config
This config file is in '/home/$YOUR_USER_NAME/.gammurc'
and config this one too:
nano /etc/gammu-smsdrc
set your connection field to 'at' and port field to 'ttyUSBx' which appear your system.
Restart your gammu-smsd service, and if it's active it should work.
service gammu-smsd restart
service gammu-smsd status
● gammu-smsd.service - SMS daemon for Gammu
Loaded: loaded (/lib/systemd/system/gammu-smsd.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2017-12-11 00:02:06 IRST; 10h ago
Docs: man:gammu-smsd(1)
Main PID: 650 (gammu-smsd)
Memory: 1.8M
CPU: 3min 8.684s
CGroup: /system.slice/gammu-smsd.service
└─650 /usr/bin/gammu-smsd --pid=/var/run/gammu-smsd.pid --daemon
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I want to use gammu for sending sms.
I have problem when want to identify the phone from gammu utility
Environment used:
- openSUSE 12.3 32-bit
- Gammu version 1.32.0 built 09:27 on Aug 10 2012 using GCC 4.7
> gammu -f /var/log/gammulog identify
No response in specified timeout. Probably phone not connected.
I make sure my modem is connected to my laptop
> lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 019: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 003 Device 002: ID 04f2:b3bb Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 005: ID 0cf3:3004 Atheros Communications, Inc.
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Then I check using this command to make sure the modem is detected
> ls /dev/serial/by-id -l
lrwxrwxrwx 1 root root 13 Oct 31 11:16 usb-HSDPA_USB_Modem_HSDPA_USB_Modem-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Oct 31 11:16 usb-HSDPA_USB_Modem_HSDPA_USB_Modem-if01-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 Oct 31 11:16 usb-HSDPA_USB_Modem_HSDPA_USB_Modem-if02-port0 -> ../../ttyUSB2
lrwxrwxrwx 1 root root 13 Oct 31 11:16 usb-HSDPA_USB_Modem_HSDPA_USB_Modem-if03-port0 -> ../../ttyUSB3
When call the gammu-detect
[gammu]
device = /dev/ttyUSB0
name = Phone on USB serial port HSDPA_USB_Modem HSDPA_USB_Modem
connection = at
[gammu1]
device = /dev/ttyUSB1
name = Phone on USB serial port HSDPA_USB_Modem HSDPA_USB_Modem
connection = at
[gammu2]
device = /dev/ttyUSB2
name = Phone on USB serial port HSDPA_USB_Modem HSDPA_USB_Modem
connection = at
[gammu3]
device = /dev/ttyUSB3
name = Phone on USB serial port HSDPA_USB_Modem HSDPA_USB_Modem
connection = at
[gammu4]
device = /dev/ttyS0
name = Phone on serial port 0
connection = at
[gammu5]
device = /dev/ttyS1
name = Phone on serial port 1
connection = at
[gammu6]
device = /dev/ttyS2
name = Phone on serial port 2
connection = at
[gammu7]
device = /dev/ttyS3
name = Phone on serial port 3
connection = at
[gammu8]
device = /dev/ttyS4
name = Phone on serial port 4
connection = at
[gammu9]
device = /dev/ttyS5
name = Phone on serial port 5
connection = at
[gammu10]
device = /dev/ttyS6
name = Phone on serial port 6
connection = at
[gammu11]
device = /dev/ttyS7
name = Phone on serial port 7
connection = at
opening socket: No such device
Here is the gammu-config, placed in /etc/gammurc
[gammu]
port = /dev/ttyUSB0
connection = at115200
logformat = textall
I really stuck, don't know what's wrong
Even when using wammu (GUI version), to detect phones
Wammu is now searching for phone:
Checking /dev/ttyUSB0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Checking /dev/ttyUSB1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Checking /dev/ttyUSB2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Checking /dev/ttyUSB3 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyUSB2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyUSB0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyUSB3 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyUSB1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
All finished, found 0 phones
No phone has been found!
Thanks
Updated
Here is add some log that happen when I specify the log file
> tail -f gammu.log
Thu 2013/10/31 11:55:14: [Gammu - 1.32.0 built 09:27 Aug 10 2012 using GCC 4.7]
Thu 2013/10/31 11:55:14: [Connection - "at"]
Thu 2013/10/31 11:55:14: [Connection index - 0]
Thu 2013/10/31 11:55:14: [Model type - ""]
Thu 2013/10/31 11:55:14: [Device - "/dev/ttyUSB0"]
Thu 2013/10/31 11:55:14: [Running on - Linux, kernel 3.7.10-1.16-desktop (#1 SMP PREEMPT Fri May 31 20:21:23 UTC 2013 (97c14ba))]
Thu 2013/10/31 11:55:14: Serial device: DTR is up, RTS is up, CAR is up, CTS is up
Thu 2013/10/31 11:55:14: Setting speed to 19200
Thu 2013/10/31 11:55:14: [Module - "auto"]
Thu 2013/10/31 11:55:14: Escaping SMS mode
Thu 2013/10/31 11:55:14: Sending simple AT command to wake up some devices
Thu 2013/10/31 11:55:14: 1 "OK"
Thu 2013/10/31 11:55:14: Checking line: OK
Thu 2013/10/31 11:55:14: AT reply state: 1
Thu 2013/10/31 11:55:14: Enabling echo
Thu 2013/10/31 11:55:15: 1 "OK"
Thu 2013/10/31 11:55:15: Checking line: OK
Thu 2013/10/31 11:55:15: AT reply state: 1
Thu 2013/10/31 11:55:15: Trying Motorola mode switch
Thu 2013/10/31 11:55:15: 1 "ERROR"
Thu 2013/10/31 11:55:15: Checking line: ERROR
Thu 2013/10/31 11:55:15: AT reply state: 3
Thu 2013/10/31 11:55:15:
Thu 2013/10/31 11:55:15: Frame not request now. If you can, please report it (see <http://wammu.eu/support/bugs/>). Thank you
Thu 2013/10/31 11:55:15: LAST SENT frame type 0x00/length 10
Thu 2013/10/31 11:55:15: 41A|54T|2B+|4DM|4FO|44D|45E|3D=|322|0D AT+MODE=2.
Thu 2013/10/31 11:55:15: RECEIVED frame type 0x00/length 0x7/7
Thu 2013/10/31 11:55:15: 45E|52R|52R|4FO|52R|0D |0A ERROR..
Thu 2013/10/31 11:55:15:
Thu 2013/10/31 11:55:17: Seems not to be supported
Thu 2013/10/31 11:55:17: Enabling CME errors
Thu 2013/10/31 11:55:17: 1 "OK"
Thu 2013/10/31 11:55:17: Checking line: OK
Thu 2013/10/31 11:55:17: AT reply state: 1
Thu 2013/10/31 11:55:17:
Thu 2013/10/31 11:55:17: Frame not request now. If you can, please report it (see <http://wammu.eu/support/bugs/>). Thank you
Thu 2013/10/31 11:55:17: LAST SENT frame type 0x00/length 10
Thu 2013/10/31 11:55:17: 41A|54T|2B+|43C|4DM|45E|45E|3D=|311|0D AT+CMEE=1.
Thu 2013/10/31 11:55:17: RECEIVED frame type 0x00/length 0x4/4
Thu 2013/10/31 11:55:17: 4FO|4BK|0D |0A OK..
Thu 2013/10/31 11:55:17:
Thu 2013/10/31 11:55:19: 1 "OK"
Thu 2013/10/31 11:55:19: Checking line: OK
Thu 2013/10/31 11:55:19: AT reply state: 1
Thu 2013/10/31 11:55:19:
Thu 2013/10/31 11:55:19: Frame not request now. If you can, please report it (see <http://wammu.eu/support/bugs/>). Thank you
Thu 2013/10/31 11:55:19: LAST SENT frame type 0x00/length 10
Thu 2013/10/31 11:55:19: 41A|54T|2B+|43C|4DM|45E|45E|3D=|322|0D AT+CMEE=2.
Thu 2013/10/31 11:55:19: RECEIVED frame type 0x00/length 0x4/4
Thu 2013/10/31 11:55:19: 4FO|4BK|0D |0A OK..
Thu 2013/10/31 11:55:19:
Thu 2013/10/31 11:55:21: CME errors could not be enabled, some error types won't be detected.
Thu 2013/10/31 11:55:21: 1 "+CSCS: "IRA""
Thu 2013/10/31 11:55:21: 2 "OK"
Thu 2013/10/31 11:55:21: Checking line: OK
Thu 2013/10/31 11:55:21: AT reply state: 1
Thu 2013/10/31 11:55:21:
Thu 2013/10/31 11:55:21: UNKNOWN frame. If you can, please report it (see <http://wammu.eu/support/bugs/>). Thank you
Thu 2013/10/31 11:55:21: LAST SENT frame type 0x00/length 9
Thu 2013/10/31 11:55:21: 41A|54T|2B+|43C|53S|43C|53S|3F?|0D AT+CSCS?.
Thu 2013/10/31 11:55:21: RECEIVED frame type 0x00/length 0x14/20
Thu 2013/10/31 11:55:21: 2B+|43C|53S|43C|53S|3A:|20 |22"|49I|52R|41A|22"|0D |0A |0D |0A +CSCS: "IRA"....
Thu 2013/10/31 11:55:21: 4FO|4BK|0D |0A OK..
Thu 2013/10/31 11:55:21:
Thu 2013/10/31 11:55:23: Init:GSM_TryGetModel failed with error TIMEOUT[14]: No response in specified timeout. Probably phone not connected.
Thu 2013/10/31 11:55:23: [Terminating]
Thu 2013/10/31 11:55:23: [Closing]
In the beginning part everything is OK
We i look more details in this part everything is success
Thu 2013/10/31 11:55:14: Sending simple AT command to wake up some devices
Thu 2013/10/31 11:55:14: 1 "OK"
Thu 2013/10/31 11:55:14: Checking line: OK
Thu 2013/10/31 11:55:14: AT reply state: 1
Thu 2013/10/31 11:55:14: Enabling echo
Thu 2013/10/31 11:55:15: 1 "OK"
Thu 2013/10/31 11:55:15: Checking line: OK
Thu 2013/10/31 11:55:15: AT reply state: 1
Error occured in this part. It's like detecting this is Motorola, but I'm using Huawei E169
Thu 2013/10/31 14:13:16: Trying Motorola mode switch
Thu 2013/10/31 14:13:16: SENDING frametype 0x00/length 0x0A/10
Thu 2013/10/31 14:13:16: 41A|54T|2B+|4DM|4FO|44D|45E|3D=|322|0D AT+MODE=2.
Thu 2013/10/31 14:13:16: 1 "ERROR"
Thu 2013/10/31 14:13:16: Checking line: ERROR
Update
I try to use other modem ZTE MF288, and it works just fine.
Still don't know how to configure Huawei E169
I'm using the Huawei E169 too, but I have only 3 Ports (ttyUSB0, ttyUSB1, ttyUSB2).
Bought it in Germany, using Ubuntu 13.10 with gammu 1.33.0.
Works fine for me when I use the highest port (ttyUSB2).
-> gammu identify
Gerät : /dev/ttyUSB2
Hersteller : Huawei
Modell : E169 (E169)
Firmware : 11.314.13.00.264
It could also be possible the device is in Storage-Mode and you need to switch it to "phone-mode".
There is a lot of information in the output but the key output appears to be.
"Seems to not be supported"
Even though gammu connects to your phone it may not be able to connect to the SMS commands.
Check here for a list of supported phones. http://wammu.eu/phones it appears that your phone is listed.
You may need to set the model in your .gammurc file. Like this model = E169