Edison serial port console becomes unresponsive when connected to Linux

Question

Edison serial port console becomes unresponsive when connected to Linux

Closed this issue 8 years ago · 10 comments

I downloaded and flashed pre-compiled Ostro project image onto Edison. When connected to Edison from Ubuntu, over the serial port, the terminal app becomes unresponsive. I need to disconnect and reconnect to gain access to serial console.

dmesg shows lot of these messages:
[ 178.915625] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 178.916999] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 178.919856] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 179.043142] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 179.044506] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 179.047299] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 179.203959] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA

I have tried SecureCRT, minicom and screen. 115200, 8N1, no flow-control.

js333031 commented 9 years ago

yes

Answer 1 · 2016-05-31T21:13:38.000Z

If I use Windows host + Tera Term, I don't see the dmesg logs (HSU serial...). The serial console is also stable w/Windows.

Answer 2 · 2016-06-01T13:21:48.000Z

The last time I tried, this was from a Fedora host (and I never saw these). Can you clarify which Ostro image you used so I can give this another go.

Answer 3 · 2016-06-01T14:07:34.000Z

I used this as well as images I'm compiling locally.

Answer 4 · 2016-06-02T14:53:33.000Z

@uhofemei , would you be able to test this?

Answer 5 · 2016-06-02T17:14:06.000Z

@js333031 are you using the same micro USB cable when connecting to the Edison from a Windows host?

Answer 6 · 2016-06-02T21:01:33.000Z

I have not seen this issue and am out of ideas how to fix this. Sorry.

Answer 7 · 2016-06-02T21:04:04.000Z

In the dmesg output below, I used my dual-boot system. First, booted into Ubuntu and connected to Edison via /dev/ttyUSB0. Then, after seeing the issue, rebooted into Windows 7. This is at timestamp 526, you can see when Windows+Edison recognized each other. The "HSU..DMA" issue isn't seen thereafter in Edison's dmesg.

[ 516.371766] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.372308] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.373555] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.871199] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.871720] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.873385] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.874216] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.875043] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.876703] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.877948] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.879196] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.880026] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 516.881269] HSU serial 0000:00:04.3: Got LSR irq(0xf8) while using DMA
[ 526.734646] dwc3-device dwc3-device.1: device suspended; notify OTG
[ 531.486769] g_multi gadget: high-speed config #2: Multifunction with CDC ECM
[ 565.978870] dwc3-device dwc3-device.1: device suspended; notify OTG
[ 568.309074] g_multi gadget: high-speed config #2: Multifunction with CDC ECM
root@edison:~#

Answer 8 · 2016-09-01T09:57:42.000Z

@js333031 Do you still see this? Have you checked your Ubuntu setup has the necessary g_* modules loaded?

Answer 9 · 2016-09-06T08:59:10.000Z

It's expected this is host PC specific. (the Edison device operates OK without reboots when changing to win)