Issue metadata
Sign in to add a comment
|
servod segfaulting, likely due to recent servo_v4 commit
Reported by
dhend...@chromium.org,
Jul 19 2016
|
||||||||||||||||||||||
Issue description
I've been unable to start servod for my ServoV2 recently due to a segfault. After a bit of backtracking it appears to begin misbehaving once CL:358881 (
servo_v4: Update default interfaces to work with servo micro) is applied.
Here's what I see:
$ sudo servod -b reef
2016-07-19 13:09:12,502 - servod - INFO - Start
2016-07-19 13:09:12,592 - servod - INFO - Found servo, vid: 0x18d1 pid: 0x5002 sid: 906533-00087
2016-07-19 13:09:12,594 - servod - INFO - Found XML overlay for board reef
2016-07-19 13:09:12,594 - SystemConfig - INFO - Loading XML config /usr/lib64/python2.7/site-packages/servo/data/servo_v2_r1.xml
2016-07-19 13:09:12,595 - SystemConfig - INFO - Loading XML config /usr/lib64/python2.7/site-packages/servo/data/servo_v2_r0.xml
2016-07-19 13:09:12,604 - SystemConfig - INFO - Loading XML config /usr/lib64/python2.7/site-packages/servo/data/common.xml
2016-07-19 13:09:12,606 - SystemConfig - INFO - Loading XML config /usr/lib64/python2.7/site-packages/servo/data/keyboard.xml
2016-07-19 13:09:12,620 - SystemConfig - INFO - Loading XML config /usr/lib64/python2.7/site-packages/servo/data/servo_reef_overlay.xml
2016-07-19 13:09:12,621 - SystemConfig - INFO - Loading XML config /usr/lib64/python2.7/site-packages/servo/data/servoflex_v2_r0_p50.xml
2016-07-19 13:09:12,622 - SystemConfig - INFO - Loading XML config /usr/lib64/python2.7/site-packages/servo/data/x86_ec_common.xml
2016-07-19 13:09:12,624 - SystemConfig - INFO - Loading XML config /usr/lib64/python2.7/site-packages/servo/data/ec_common.xml
2016-07-19 13:09:12,633 - Servod - INFO - Initializing interface 2 to ftdi_i2c
2016-07-19 13:09:12,641 - Servod - INFO - Initializing interface 3 to ftdi_uart
2016-07-19 13:09:12,647 - Servod - INFO - /dev/pts/76
2016-07-19 13:09:12,647 - Servod - INFO - Initializing interface 4 to ftdi_uart
2016-07-19 13:09:12,651 - Servod - INFO - /dev/pts/77
2016-07-19 13:09:12,651 - Servod - INFO - Initializing interface 7 to ftdi_uart
-E- :: Opening usb connection: unable to claim usb device. Make sure the default FTDI driver is not in use
-E- :: vid:0x18d1 pid:0x5002 serial:906533-00087
Traceback (most recent call last):
File "/usr/lib/python-exec/python2.7/servod", line 9, in <module>
load_entry_point('servo===0.0.1-5c66721', 'console_scripts', 'servod')()
File "/usr/lib64/python2.7/site-packages/servo/servod.py", line 515, in main
main_function()
File "/usr/lib64/python2.7/site-packages/servo/servod.py", line 504, in main_function
usbkm232=options.usbkm232)
File "/usr/lib64/python2.7/site-packages/servo/servo_server.py", line 131, in __init__
result = func(interface)
File "/usr/lib64/python2.7/site-packages/servo/servo_server.py", line 334, in _init_ftdi_uart
raise ServodError('Running uart interface. %s ( %d )' % (e.msg, e.value))
servo.servo_server.ServodError: Running uart interface. doing fuart_open ( -1 )
failed ftdi_read_data: Bad file descriptor
-E- :: reading ftdi data: (null)
Segmentation fault (core dumped)
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kevcheng@chromium.org
, Jul 19 2016Status: Duplicate (was: Assigned)