Bug 1447404 - moserial freeze after a connection
Summary: moserial freeze after a connection
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: moserial
Version: 25
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Terje Røsten
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-02 15:57 UTC by giaborc
Modified: 2017-12-12 10:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:06:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
jorunalctl -f when the application freezed (3.36 KB, text/plain)
2017-05-02 15:57 UTC, giaborc
no flags Details

Description giaborc 2017-05-02 15:57:14 UTC
Created attachment 1275718 [details]
jorunalctl -f when the application freezed

Description of problem:
moserial freeze after a connection with ttyUSBO, 9600 baud, 8 bit, 1 bit stop, no parity. ttyUSB0 is connected to a USB/serial adapter with cp2102 chip.
Using cat /dev/ttyUSB0 serial connection works flawlessly. No error are reported just a freeze that i had to kill -9 to close the program.

Version-Release number of selected component (if applicable):

3.0.11-1.fc25 
How reproducible:
Every time i try to connect just freeze.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 giaborc 2017-05-12 13:15:17 UTC
UPDATE:
If I disconnect the usb/serial adapter moserial unfreeze and i get the data from the conneted device(AVR chip).
dmesg output:
[ 4199.898177] usb 7-1: cp210x converter now attached to ttyUSB0
[ 4255.250678] cp210x ttyUSB0: failed to get comm status: -71
[ 4255.271672] cp210x ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
[ 4255.272673] cp210x ttyUSB0: failed to get comm status: -71
[ 4255.302678] cp210x ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
[ 4255.303674] cp210x ttyUSB0: failed to get comm status: -71
[ 4255.456074] usb 7-1: USB disconnect, device number 8
[ 4255.456689] cp210x ttyUSB0: failed set request 0x12 status: -19
[ 4255.456694] cp210x ttyUSB0: failed set request 0x0 status: -19
[ 4255.456857] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 4255.456869] cp210x 7-1:1.0: device disconnected

Comment 2 Fedora End Of Life 2017-11-16 19:54:51 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:06:02 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.