Bug 773413 - can't establish console connection with usbserial
Summary: can't establish console connection with usbserial
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: ppc64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-11 19:01 UTC by Kevin W Monroe
Modified: 2012-11-14 15:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-14 15:23:28 UTC
Type: ---


Attachments (Terms of Use)

Description Kevin W Monroe 2012-01-11 19:01:35 UTC
Description of problem:
I'm using a Power Mac G5 and have a Targus USB to Serial adapter (PA088UZ) connected to a null modem cable connected to an ubuntu box's ttyS0. The /dev/ttyUSB0 device seems to be correctly created and syslog shows the mct_u232 module loading. However, neither minicom nor gtkterm display data sent from ttyS0. Echo/cat'ing to ttyUSB0 doesn't show up on the ttyS0 side either.

I'll put relevant syslog info below, but it's worth mentioning that an f15 intel box works as expected (both minicom and echo). I'll try to get f16 on that machine to see if this is a ppc64 thing or an f16 thing.

This problem was first seen (and is reproducible) using the stock fc16.ppc64 kernel. I changed the config to make usbserial a module for ease of un/loading. The problem exists whether usbserial is built-in or not. My local config diffs just fyi:

-CONFIG_USB_SERIAL=y
-CONFIG_USB_SERIAL_CONSOLE=y
+CONFIG_USB_SERIAL=m

Version-Release number of selected component (if applicable):
kernel-3.1.5-6.fc16.ppc64

How reproducible:
Always

Steps to Reproduce:
1. Wire USB port<->USBtoSerial<->null modem<->serial port
2. Verify /dev/ttyUSB0 is created on the ppc64 box
3. On the ttyS0 box: minicom -D /dev/ttyS0
4. On the ppc64 box: echo "this is unfortunate" > /dev/ttyUSB0
  
Actual results:
no data seen in minicom 

Expected results:
Welcome to minicom 2.5

OPTIONS: I18n 
Compiled on Feb  5 2011, 06:31:42.
Port /dev/ttyS0

Press CTRL-A Z for help on special keys              
                                                     
this is unfortunate X4 &c1 E1 Q0

Additional info:
I loaded usbserial and mct_u232 with debug=1, but that didn't get me much. Output from /var/log/messages:

$ sudo modprobe usbserial debug=1
Jan 11 12:57:09 devbox kernel: [ 3971.856070] usbcore: registered new interface driver usbserial
Jan 11 12:57:09 devbox kernel: [ 3971.856219] USB Serial support registered for generic
Jan 11 12:57:09 devbox kernel: [ 3971.856313] usbcore: registered new interface driver usbserial_generic
Jan 11 12:57:09 devbox kernel: [ 3971.856318] usbserial: USB Serial Driver core

$ sudo modprobe mct_u232 debug=1
Jan 11 12:58:01 devbox kernel: [ 4024.742855] USB Serial support registered for MCT U232
Jan 11 12:58:01 devbox kernel: [ 4024.742945] usbcore: registered new interface driver mct_u232
Jan 11 12:58:01 devbox kernel: [ 4024.742950] mct_u232: z2.1:Magic Control Technology USB-RS232 converter driver

### Plug in the Targus ###
Jan 11 12:58:43 devbox kernel: [ 4066.172232] usb 2-2: new full speed USB device number 3 using ohci_hcd
Jan 11 12:58:43 devbox kernel: [ 4066.405263] usb 2-2: New USB device found, idVendor=0711, idProduct=0230
Jan 11 12:58:43 devbox kernel: [ 4066.405275] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 11 12:58:43 devbox kernel: [ 4066.405282] usb 2-2: Product: Targus Group Intl
Jan 11 12:58:43 devbox kernel: [ 4066.405288] usb 2-2: Manufacturer: Targus Group Intl            
Jan 11 12:58:43 devbox kernel: [ 4066.405294] usb 2-2: SerialNumber: 473262
Jan 11 12:58:43 devbox kernel: [ 4066.408520] mct_u232 2-2:1.0: MCT U232 converter detected
Jan 11 12:58:43 devbox kernel: [ 4066.409035] usb 2-2: MCT U232 converter now attached to ttyUSB0
Jan 11 12:58:43 devbox mtp-probe: checking bus 2, device 3: "/sys/devices/pci0001:00/0001:00:08.0/0001:01:0b.0/usb2/2-2"
Jan 11 12:58:43 devbox mtp-probe: bus: 2, device: 3 was not an MTP device

Comment 1 Kevin W Monroe 2012-01-11 20:50:04 UTC
FYI, i tried kernel-2.6.39-1.fc16.ppc64 with no luck. Problem still exists.

Comment 2 Dave Jones 2012-03-22 17:11:20 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 3 Dave Jones 2012-03-22 17:13:49 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 4 Dave Jones 2012-03-22 17:23:09 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 5 Kevin W Monroe 2012-08-09 19:11:22 UTC
Same Targus usbserial adapter, same results from ppc64 ttyUSB0 to intel ttyS0: no output is seen from either side of the serial connection. This time on fedora 17:

$ rpm -q kernel
kernel-3.4.4-5.fc17.ppc64

I've tried various combinations of flow control settings and speeds; none resolve the problem. I wired up 2 intel f17 boxes as described in comment 0 and the results look fine.

From ttyUSB0 box:
# echo "this is unfortunate" > /dev/ttyUSB0

On ttyS0 box running 'minicom -D /dev/ttyS0':
Welcome to minicom 2.5

OPTIONS: I18n 
Compiled on May  2 2011, 00:39:27.
Port /dev/ttyS0

Press CTRL-A Z for help on special keys

this is unfortunate 

I'm fairly certain this points to usbserial on ppc64 as the problem. Let me know if there's any debug info or testing I can provide to help resolve this.

Comment 6 Kevin W Monroe 2012-08-09 21:13:00 UTC
Good news!  Well, decent news. I swapped the Targus (mct_u232) with a Trendnet (pl2303) and the test from comment 0 works like a champ.

I imagine this is a pretty low priority given the secondary arch and dwindling population of folks that want serial connectivity on a powermac, but I'd be happy to test any mct_u232 updates as they come along.

Comment 7 Dave Jones 2012-10-23 15:33:56 UTC
# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 8 Justin M. Forbes 2012-11-14 15:23:28 UTC
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.


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