Linux-USB Archive on lore.kernel.org
 help / color / Atom feed
* Re: problems with Edgeport/416
       [not found]     ` <20190821122028.GA19107@kroah.com>
@ 2019-08-21 13:04       ` walter harms
  2019-08-21 13:20         ` AW: " Schmid, Carsten
  2019-08-21 13:36         ` Greg KH
  0 siblings, 2 replies; 8+ messages in thread
From: walter harms @ 2019-08-21 13:04 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-usb, Schmid, Carsten



Am 21.08.2019 14:20, schrieb Greg KH:
> On Wed, Aug 21, 2019 at 01:48:46PM +0200, walter harms wrote:
>>
>>
>> Am 21.08.2019 13:20, schrieb Greg KH:
>>> On Wed, Aug 21, 2019 at 12:27:24PM +0200, walter harms wrote:
>>>> Hello List,
>>>> does some use linux with an Edgeport/416 ?
>>>>
>>>> I have a strange problem. the device is resetting soon
>>>> after i started using it (but not immediately).
>>>> I do not see a kernel OOPS but a common pattern is:
>>>>
>>>> 2019-08-20T15:19:39.825812+00:00 omnfrmo10 kernel: [683270.658623] usb 7-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>>> 2019-08-20T15:19:39.825818+00:00 omnfrmo10 kernel: [683270.658626] usb 7-1.1.2: Product: Edgeport/416
>>>> 2019-08-20T15:19:39.825821+00:00 omnfrmo10 kernel: [683270.658628] usb 7-1.1.2: Manufacturer: Digi International
>>>> 2019-08-20T15:19:39.825823+00:00 omnfrmo10 kernel: [683270.658630] usb 7-1.1.2: SerialNumber: E63966100-1
>>>> 2019-08-20T15:19:39.985571+00:00 omnfrmo10 kernel: [683270.817909] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB4
>>>> 2019-08-20T15:19:39.985594+00:00 omnfrmo10 kernel: [683270.818132] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB5
>>>> 2019-08-20T15:19:40.007943+00:00 omnfrmo10 mtp-probe: checking bus 7, device 88: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.2"
>>>> 2019-08-20T15:19:40.053750+00:00 omnfrmo10 kernel: [683270.885626] usb 7-1.2.2: New USB device found, idVendor=1608, idProduct=0247
>>>> 2019-08-20T15:19:40.053791+00:00 omnfrmo10 kernel: [683270.885630] usb 7-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>>> 2019-08-20T15:19:40.053797+00:00 omnfrmo10 kernel: [683270.885633] usb 7-1.2.2: Product: Edgeport/416
>>>> 2019-08-20T15:19:40.053800+00:00 omnfrmo10 kernel: [683270.885635] usb 7-1.2.2: Manufacturer: Digi International
>>>> 2019-08-20T15:19:40.053803+00:00 omnfrmo10 kernel: [683270.885637] usb 7-1.2.2: SerialNumber: E63966100-5
>>>> 2019-08-20T15:19:40.065569+00:00 omnfrmo10 kernel: [683270.897406] usb 7-1.1.3: new full-speed USB device number 90 using uhci_hcd
>>>> 2019-08-20T15:19:40.213569+00:00 omnfrmo10 kernel: [683271.046316] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB6
>>>> 2019-08-20T15:19:40.213594+00:00 omnfrmo10 kernel: [683271.046782] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB7
>>>> 2019-08-20T15:19:40.242034+00:00 omnfrmo10 mtp-probe: checking bus 7, device 89: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.2/7-1.2.2"
>>>> 2019-08-20T15:19:40.301578+00:00 omnfrmo10 kernel: [683271.133380] usb 7-1.2.3: new full-speed USB device number 91 using uhci_hcd
>>>> 2019-08-20T15:19:40.357559+00:00 omnfrmo10 kernel: [683271.192815] usb 7-1.1.3: New USB device found, idVendor=1608, idProduct=0247
>>>> 2019-08-20T15:19:40.357584+00:00 omnfrmo10 kernel: [683271.192820] usb 7-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>>> 2019-08-20T15:19:40.357588+00:00 omnfrmo10 kernel: [683271.192822] usb 7-1.1.3: Product: Edgeport/416
>>>> 2019-08-20T15:19:40.357591+00:00 omnfrmo10 kernel: [683271.192825] usb 7-1.1.3: Manufacturer: Digi International
>>>> 2019-08-20T15:19:40.357593+00:00 omnfrmo10 kernel: [683271.192827] usb 7-1.1.3: SerialNumber: E63966100-2
>>>> 2019-08-20T15:19:40.513702+00:00 omnfrmo10 kernel: [683271.349103] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB8
>>>> 2019-08-20T15:19:40.513725+00:00 omnfrmo10 kernel: [683271.349311] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB9
>>>> 2019-08-20T15:19:40.537138+00:00 omnfrmo10 mtp-probe: checking bus 7, device 90: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.3"
>>>> 2019-08-20T15:19:40.601754+00:00 omnfrmo10 kernel: [683271.433389] usb 7-1.1.4: new full-speed USB device number 92 using uhci_hcd
>>>> 2019-08-20T15:19:40.601794+00:00 omnfrmo10 kernel: [683271.433631] usb 7-1.2.3: New USB device found, idVendor=1608, idProduct=0247
>>>> 2019-08-20T15:19:40.601798+00:00 omnfrmo10 kernel: [683271.433634] usb 7-1.2.3: New USB device strings: Mfr=1, Produc
>>>
>>> I don't see any errors there.  What is the problem with the device?
>>>
>> You use it, it resets (ports gone etc) and appears again.
>> I suspected that the device is broken but i test today with windows
>> (and a different computer) showed it works fine.
> 
> Different computer?  Did you try windows on the same exact machine with
> same exact cable?  This sounds like a hardware program, if the device
> disconnects,there's nothing the software can do about that, it's a
> hardware / electrical thing.
> 

Different computer but same cables i guess the device is ok.

NTL I found that little gem:
https://www.fclose.com/linux-kernels/594677/usb-io_ti-add-heartbeat-to-keep-idle-ep-416-ports-from-disconnecting-linux-4-3/

The behavior would fit (any way to check that the heartbeat is active ?).

Casten Schmidt ask me to look into /sys/kernel/debug/dynamic_debug/control before i start to
debug the whole usb part, is that below expected behavior ? (i tried to find what version of edgeport the driver suspects).

drivers/usb/serial/io_ti.c:1507 [io_ti]do_boot_mode =_ "%s - STAYING IN BOOT MODE\012"
drivers/usb/serial/io_ti.c:1500 [io_ti]do_boot_mode =_ "%s - Download successful -- Device rebooting...\012"
drivers/usb/serial/io_ti.c:1493 [io_ti]do_boot_mode =_ "%s - Error downloading operational code image\012"
drivers/usb/serial/io_ti.c:1487 [io_ti]do_boot_mode =_ "%s - Downloading operational code image version %d.%d (TI UMP)\012"
drivers/usb/serial/io_ti.c:1440 [io_ti]do_boot_mode =_ "%s - Wrong CPU Rev %d (Must be 2)\012"
drivers/usb/serial/io_ti.c:1403 [io_ti]do_boot_mode =_ "%s - VID = 0x%x\012"
drivers/usb/serial/io_ti.c:1393 [io_ti]do_boot_mode =_ "%s - RUNNING IN BOOT MODE\012"
drivers/usb/serial/io_ti.c:1367 [io_ti]do_download_mode =_ "%s - Update complete 0x%x\012"
drivers/usb/serial/io_ti.c:1358 [io_ti]do_download_mode =_ "%s - Start firmware update\012"
drivers/usb/serial/io_ti.c:1347 [io_ti]do_download_mode =_ "%s - write download record failed\012"
drivers/usb/serial/io_ti.c:1338 [io_ti]do_download_mode =_ "%s - can't read header back\012"
drivers/usb/serial/io_ti.c:1291 [io_ti]do_download_mode =_ "%s - Found Type BLANK FIRMWARE (Type F2) record\012"
drivers/usb/serial/io_ti.c:1252 [io_ti]do_download_mode =_ "%s - HARDWARE RESET return %d\012"
drivers/usb/serial/io_ti.c:1243 [io_ti]do_download_mode =_ "%s - HARDWARE RESET\012"
drivers/usb/serial/io_ti.c:1178 [io_ti]do_download_mode =_ "%s - Update I2C dld from %d.%d to %d.%d\012"
drivers/usb/serial/io_ti.c:1166 [io_ti]do_download_mode =_ "%s - >> FW Versions Device %d.%d  Driver %d.%d\012"
drivers/usb/serial/io_ti.c:1129 [io_ti]do_download_mode =_ "%s - Found Type FIRMWARE (Type 2) record\012"
drivers/usb/serial/io_ti.c:1110 [io_ti]do_download_mode =_ "%s - Wrong CPU Rev %d (Must be 2)\012"
drivers/usb/serial/io_ti.c:1089 [io_ti]do_download_mode =_ "%s - DOWNLOAD MODE -- BAD I2C\012"
drivers/usb/serial/io_ti.c:1085 [io_ti]do_download_mode =_ "%s - RUNNING IN DOWNLOAD MODE\012"
drivers/usb/serial/io_ti.c:906 [io_ti]i2c_type_bootmode =_ "%s - Unknown\012"
drivers/usb/serial/io_ti.c:901 [io_ti]i2c_type_bootmode =_ "%s - ROM_TYPE_III\012"
drivers/usb/serial/io_ti.c:899 [io_ti]i2c_type_bootmode =_ "%s - read 2 data = 0x%x\012"
drivers/usb/serial/io_ti.c:897 [io_ti]i2c_type_bootmode =_ "%s - read 3 status error = %d\012"
drivers/usb/serial/io_ti.c:888 [io_ti]i2c_type_bootmode =_ "%s - ROM_TYPE_II\012"
drivers/usb/serial/io_ti.c:886 [io_ti]i2c_type_bootmode =_ "%s - read 2 data = 0x%x\012"
drivers/usb/serial/io_ti.c:884 [io_ti]i2c_type_bootmode =_ "%s - read 2 status error = %d\012"

re,
 wh

^ permalink raw reply	[flat|nested] 8+ messages in thread

* AW: problems with Edgeport/416
  2019-08-21 13:04       ` problems with Edgeport/416 walter harms
@ 2019-08-21 13:20         ` " Schmid, Carsten
  2019-08-21 13:40           ` walter harms
  2019-08-21 13:36         ` Greg KH
  1 sibling, 1 reply; 8+ messages in thread
From: Schmid, Carsten @ 2019-08-21 13:20 UTC (permalink / raw)
  To: wharms, Greg KH; +Cc: linux-usb

> 
> Different computer but same cables i guess the device is ok.
> 
But maybe the USB  port of the computer is broken.

> NTL I found that little gem:
> https://www.fclose.com/linux-kernels/594677/usb-io_ti-add-heartbeat-to-
> keep-idle-ep-416-ports-from-disconnecting-linux-4-3/
> 
> The behavior would fit (any way to check that the heartbeat is active ?).
> 
Which kernel are you running on?
use "uname -a" to get it.
This patch was introduced in 4.3 kernel, not really hot ...
And, yes, looks like what you experience.

> Casten Schmidt ask me to look into
> /sys/kernel/debug/dynamic_debug/control before i start to
> debug the whole usb part, is that below expected behavior ? (i tried to find
> what version of edgeport the driver suspects).
> 
> drivers/usb/serial/io_ti.c:1507 [io_ti]do_boot_mode =_ "%s - STAYING IN BOOT MODE\012"
...
> drivers/usb/serial/io_ti.c:884 [io_ti]i2c_type_bootmode =_ "%s - read 2 status error = %d\012"
> 
That says that we have dynamic debug messages available for the driver.
If you enable those by doing
echo -n 'module io_ti =p' > /sys/kernel/debug/dynamic_debug/control

Then you should see at least some of those messages appear in dmesg (kernel log).

Best regards
Carsten

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: problems with Edgeport/416
  2019-08-21 13:04       ` problems with Edgeport/416 walter harms
  2019-08-21 13:20         ` AW: " Schmid, Carsten
@ 2019-08-21 13:36         ` Greg KH
  1 sibling, 0 replies; 8+ messages in thread
From: Greg KH @ 2019-08-21 13:36 UTC (permalink / raw)
  To: walter harms; +Cc: linux-usb, Schmid, Carsten

On Wed, Aug 21, 2019 at 03:04:48PM +0200, walter harms wrote:
> 
> 
> Am 21.08.2019 14:20, schrieb Greg KH:
> > On Wed, Aug 21, 2019 at 01:48:46PM +0200, walter harms wrote:
> >>
> >>
> >> Am 21.08.2019 13:20, schrieb Greg KH:
> >>> On Wed, Aug 21, 2019 at 12:27:24PM +0200, walter harms wrote:
> >>>> Hello List,
> >>>> does some use linux with an Edgeport/416 ?
> >>>>
> >>>> I have a strange problem. the device is resetting soon
> >>>> after i started using it (but not immediately).
> >>>> I do not see a kernel OOPS but a common pattern is:
> >>>>
> >>>> 2019-08-20T15:19:39.825812+00:00 omnfrmo10 kernel: [683270.658623] usb 7-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> >>>> 2019-08-20T15:19:39.825818+00:00 omnfrmo10 kernel: [683270.658626] usb 7-1.1.2: Product: Edgeport/416
> >>>> 2019-08-20T15:19:39.825821+00:00 omnfrmo10 kernel: [683270.658628] usb 7-1.1.2: Manufacturer: Digi International
> >>>> 2019-08-20T15:19:39.825823+00:00 omnfrmo10 kernel: [683270.658630] usb 7-1.1.2: SerialNumber: E63966100-1
> >>>> 2019-08-20T15:19:39.985571+00:00 omnfrmo10 kernel: [683270.817909] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB4
> >>>> 2019-08-20T15:19:39.985594+00:00 omnfrmo10 kernel: [683270.818132] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB5
> >>>> 2019-08-20T15:19:40.007943+00:00 omnfrmo10 mtp-probe: checking bus 7, device 88: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.2"
> >>>> 2019-08-20T15:19:40.053750+00:00 omnfrmo10 kernel: [683270.885626] usb 7-1.2.2: New USB device found, idVendor=1608, idProduct=0247
> >>>> 2019-08-20T15:19:40.053791+00:00 omnfrmo10 kernel: [683270.885630] usb 7-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> >>>> 2019-08-20T15:19:40.053797+00:00 omnfrmo10 kernel: [683270.885633] usb 7-1.2.2: Product: Edgeport/416
> >>>> 2019-08-20T15:19:40.053800+00:00 omnfrmo10 kernel: [683270.885635] usb 7-1.2.2: Manufacturer: Digi International
> >>>> 2019-08-20T15:19:40.053803+00:00 omnfrmo10 kernel: [683270.885637] usb 7-1.2.2: SerialNumber: E63966100-5
> >>>> 2019-08-20T15:19:40.065569+00:00 omnfrmo10 kernel: [683270.897406] usb 7-1.1.3: new full-speed USB device number 90 using uhci_hcd
> >>>> 2019-08-20T15:19:40.213569+00:00 omnfrmo10 kernel: [683271.046316] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB6
> >>>> 2019-08-20T15:19:40.213594+00:00 omnfrmo10 kernel: [683271.046782] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB7
> >>>> 2019-08-20T15:19:40.242034+00:00 omnfrmo10 mtp-probe: checking bus 7, device 89: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.2/7-1.2.2"
> >>>> 2019-08-20T15:19:40.301578+00:00 omnfrmo10 kernel: [683271.133380] usb 7-1.2.3: new full-speed USB device number 91 using uhci_hcd
> >>>> 2019-08-20T15:19:40.357559+00:00 omnfrmo10 kernel: [683271.192815] usb 7-1.1.3: New USB device found, idVendor=1608, idProduct=0247
> >>>> 2019-08-20T15:19:40.357584+00:00 omnfrmo10 kernel: [683271.192820] usb 7-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> >>>> 2019-08-20T15:19:40.357588+00:00 omnfrmo10 kernel: [683271.192822] usb 7-1.1.3: Product: Edgeport/416
> >>>> 2019-08-20T15:19:40.357591+00:00 omnfrmo10 kernel: [683271.192825] usb 7-1.1.3: Manufacturer: Digi International
> >>>> 2019-08-20T15:19:40.357593+00:00 omnfrmo10 kernel: [683271.192827] usb 7-1.1.3: SerialNumber: E63966100-2
> >>>> 2019-08-20T15:19:40.513702+00:00 omnfrmo10 kernel: [683271.349103] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB8
> >>>> 2019-08-20T15:19:40.513725+00:00 omnfrmo10 kernel: [683271.349311] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB9
> >>>> 2019-08-20T15:19:40.537138+00:00 omnfrmo10 mtp-probe: checking bus 7, device 90: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.3"
> >>>> 2019-08-20T15:19:40.601754+00:00 omnfrmo10 kernel: [683271.433389] usb 7-1.1.4: new full-speed USB device number 92 using uhci_hcd
> >>>> 2019-08-20T15:19:40.601794+00:00 omnfrmo10 kernel: [683271.433631] usb 7-1.2.3: New USB device found, idVendor=1608, idProduct=0247
> >>>> 2019-08-20T15:19:40.601798+00:00 omnfrmo10 kernel: [683271.433634] usb 7-1.2.3: New USB device strings: Mfr=1, Produc
> >>>
> >>> I don't see any errors there.  What is the problem with the device?
> >>>
> >> You use it, it resets (ports gone etc) and appears again.
> >> I suspected that the device is broken but i test today with windows
> >> (and a different computer) showed it works fine.
> > 
> > Different computer?  Did you try windows on the same exact machine with
> > same exact cable?  This sounds like a hardware program, if the device
> > disconnects,there's nothing the software can do about that, it's a
> > hardware / electrical thing.
> > 
> 
> Different computer but same cables i guess the device is ok.

So the device works, but the connection to your other computer probably
does not.  I'm betting this is an electrical issue :)

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: problems with Edgeport/416
  2019-08-21 13:20         ` AW: " Schmid, Carsten
@ 2019-08-21 13:40           ` walter harms
  2019-08-21 14:12             ` AW: " Schmid, Carsten
  0 siblings, 1 reply; 8+ messages in thread
From: walter harms @ 2019-08-21 13:40 UTC (permalink / raw)
  To: Schmid, Carsten; +Cc: Greg KH, linux-usb

[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]



Am 21.08.2019 15:20, schrieb Schmid, Carsten:
>>
>> Different computer but same cables i guess the device is ok.
>>
> But maybe the USB  port of the computer is broken.
> 
>> NTL I found that little gem:
>> https://www.fclose.com/linux-kernels/594677/usb-io_ti-add-heartbeat-to-
>> keep-idle-ep-416-ports-from-disconnecting-linux-4-3/
>>
>> The behavior would fit (any way to check that the heartbeat is active ?).
>>
> Which kernel are you running on?
> use "uname -a" to get it.
> This patch was introduced in 4.3 kernel, not really hot ...
> And, yes, looks like what you experience.
> 

mea culpa, i had a typo in the first msg to greg so you did not see my first post:

I tested with: Opensuse 15.1 on a DELL latitude E5400

 uname -a
 Linux omnfrmo10 4.12.14-lp151.28.10-vanilla #1 SMP Sat Jul 13 17:59:31 UTC 2019 (0ab03b7) x86_64 x86_64 x86_64 GNU/Linux

 I did some experiments (changing cables etc) but always the same. But
 when tested with a windows system it worked all fine.  later i used a
 single port USB->Serial and all worked as expected.



>> Casten Schmidt ask me to look into
>> /sys/kernel/debug/dynamic_debug/control before i start to
>> debug the whole usb part, is that below expected behavior ? (i tried to find
>> what version of edgeport the driver suspects).
>>
>> drivers/usb/serial/io_ti.c:1507 [io_ti]do_boot_mode =_ "%s - STAYING IN BOOT MODE\012"
> ...
>> drivers/usb/serial/io_ti.c:884 [io_ti]i2c_type_bootmode =_ "%s - read 2 status error = %d\012"
>>
> That says that we have dynamic debug messages available for the driver.
> If you enable those by doing
> echo -n 'module io_ti =p' > /sys/kernel/debug/dynamic_debug/control
> 
> Then you should see at least some of those messages appear in dmesg (kernel log).
> 

i see a lot, see attached file


[-- Attachment #2: edge.log.gz --]
[-- Type: application/x-gzip, Size: 13989 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* AW: problems with Edgeport/416
  2019-08-21 13:40           ` walter harms
@ 2019-08-21 14:12             ` " Schmid, Carsten
       [not found]               ` <5D5D51FF.5010400@bfs.de>
  0 siblings, 1 reply; 8+ messages in thread
From: Schmid, Carsten @ 2019-08-21 14:12 UTC (permalink / raw)
  To: wharms; +Cc: Greg KH, linux-usb

> 
>  uname -a
>  Linux omnfrmo10 4.12.14-lp151.28.10-vanilla #1 SMP Sat Jul 13 17:59:31 UTC
> 2019 (0ab03b7) x86_64 x86_64 x86_64 GNU/Linux
> 
4.12.14 - it should have the heartbeat patch introduced in 4.3

> i see a lot, see attached file
The dyndbg for the driver is active :-)

The log you sent does not show something irregular.
Can you collect the log "around a device reset" in the same way please?

Best regards
Carsten

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: problems with Edgeport/416
       [not found]                 ` <2ae1fb935c2041f8b0d54e311e730ba5@SVR-IES-MBX-03.mgc.mentorg.com>
@ 2019-08-23 15:27                   ` walter harms
  0 siblings, 0 replies; 8+ messages in thread
From: walter harms @ 2019-08-23 15:27 UTC (permalink / raw)
  To: Schmid, Carsten; +Cc: linux-usb



Am 21.08.2019 16:24, schrieb Schmid, Carsten:
>>
>> this should it be,
>>
> Suspicious: line 141 of the log:
> [765647.193393] usb 7-1.1.2: reset full-speed USB device number 15 using uhci_hcd
> 
> Can you please collect another log around reset, additionally enabling uhci dyndbg using
> echo -n 'module uhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control
> 


Just to close the problem:
I have installed the  Edgeport/416 on a different pc

Linux  4.12.14-lp150.12.25-default #1 SMP Thu Nov 1 06:14:23 UTC 2018 (3fcf457) x86_64 x86_64 x86_64 GNU/Linux
With opensuse 15.0

the one with the problem was:
Linux  4.12.14-lp151.28.10-vanilla #1 SMP Sat Jul 13 17:59:31 UTC 2019 (0ab03b7) x86_64 x86_64 x86_64 GNU/Linux


the far the device works as expected (to my surprise). So it seems to be a broken USB, why it fails
with the edgeport but not with the pl2303 (usb->rs232 someone) i used for comparison; no idea.

sorry for the noise,

re,
 wh

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: problems with Edgeport/416
  2019-08-21 11:43 ` AW: " Schmid, Carsten
@ 2019-08-21 12:03   ` walter harms
  0 siblings, 0 replies; 8+ messages in thread
From: walter harms @ 2019-08-21 12:03 UTC (permalink / raw)
  To: Schmid, Carsten; +Cc: linux-usb, greg



Am 21.08.2019 13:43, schrieb Schmid, Carsten:
> Hi Walter,
> 
> i had a similar issue with a different device.
> Please check, if you have dynamic debug enabled in your kernel
> (/sys/kernel/debug/dynamic_debug/control exists)
> 


ll /sys/kernel/debug/dynamic_debug/control
-rw-r--r-- 1 root root 0 Aug 12 16:15 /sys/kernel/debug/dynamic_debug/control


> Then you can enable additional kernel messages using
> echo -n 'module xhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control
> echo -n 'module usbcore =p' > /sys/kernel/debug/dynamic_debug/control
> 


> Check which usb related messages you can enable through the dynamic_debug.
> (doing a "cat /sys/kernel/debug/dynamic_debug/control | grep usb" helps much)
> 
I see a bunch of messages. what do you expect me to do ? I have 412 lines, should
i send them ?



> Finally, a fine resource is
> https://www.kernel.org/doc/html/v4.11/admin-guide/dynamic-debug-howto.html
> 
I did not know about dynamic-debug, fortunately linux drivers simply work these days :)

re,
 wh


> Best regards
> Carsten
> 
>> -----Ursprüngliche Nachricht-----
>> Von: linux-usb-owner@vger.kernel.org [mailto:linux-usb-
>> owner@vger.kernel.org] Im Auftrag von walter harms
>> Gesendet: Mittwoch, 21. August 2019 13:18
>> An: linux-usb@vger.kernel.org
>> Cc: greg@kroah.com
>> Betreff: problems with Edgeport/416
>>
>> Hello List,
>> does some use linux with an Edgeport/416 ?
>>
>> I have a strange problem. the device is resetting soon
>> after i started using it (but not immediately).
>> I do not see a kernel OOPS but a common pattern is:
>>
>> 2019-08-20T15:19:39.825812+00:00 omnfrmo10 kernel: [683270.658623] usb
>> 7-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> 2019-08-20T15:19:39.825818+00:00 omnfrmo10 kernel: [683270.658626] usb
>> 7-1.1.2: Product: Edgeport/416
>> 2019-08-20T15:19:39.825821+00:00 omnfrmo10 kernel: [683270.658628] usb
>> 7-1.1.2: Manufacturer: Digi International
>> 2019-08-20T15:19:39.825823+00:00 omnfrmo10 kernel: [683270.658630] usb
>> 7-1.1.2: SerialNumber: E63966100-1
>> 2019-08-20T15:19:39.985571+00:00 omnfrmo10 kernel: [683270.817909] usb
>> 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB4
>> 2019-08-20T15:19:39.985594+00:00 omnfrmo10 kernel: [683270.818132] usb
>> 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB5
>> 2019-08-20T15:19:40.007943+00:00 omnfrmo10 mtp-probe: checking bus 7,
>> device 88: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.2"
>> 2019-08-20T15:19:40.053750+00:00 omnfrmo10 kernel: [683270.885626] usb
>> 7-1.2.2: New USB device found, idVendor=1608, idProduct=0247
>> 2019-08-20T15:19:40.053791+00:00 omnfrmo10 kernel: [683270.885630] usb
>> 7-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> 2019-08-20T15:19:40.053797+00:00 omnfrmo10 kernel: [683270.885633] usb
>> 7-1.2.2: Product: Edgeport/416
>> 2019-08-20T15:19:40.053800+00:00 omnfrmo10 kernel: [683270.885635] usb
>> 7-1.2.2: Manufacturer: Digi International
>> 2019-08-20T15:19:40.053803+00:00 omnfrmo10 kernel: [683270.885637] usb
>> 7-1.2.2: SerialNumber: E63966100-5
>> 2019-08-20T15:19:40.065569+00:00 omnfrmo10 kernel: [683270.897406] usb
>> 7-1.1.3: new full-speed USB device number 90 using uhci_hcd
>> 2019-08-20T15:19:40.213569+00:00 omnfrmo10 kernel: [683271.046316] usb
>> 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB6
>> 2019-08-20T15:19:40.213594+00:00 omnfrmo10 kernel: [683271.046782] usb
>> 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB7
>> 2019-08-20T15:19:40.242034+00:00 omnfrmo10 mtp-probe: checking bus 7,
>> device 89: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.2/7-1.2.2"
>> 2019-08-20T15:19:40.301578+00:00 omnfrmo10 kernel: [683271.133380] usb
>> 7-1.2.3: new full-speed USB device number 91 using uhci_hcd
>> 2019-08-20T15:19:40.357559+00:00 omnfrmo10 kernel: [683271.192815] usb
>> 7-1.1.3: New USB device found, idVendor=1608, idProduct=0247
>> 2019-08-20T15:19:40.357584+00:00 omnfrmo10 kernel: [683271.192820] usb
>> 7-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> 2019-08-20T15:19:40.357588+00:00 omnfrmo10 kernel: [683271.192822] usb
>> 7-1.1.3: Product: Edgeport/416
>> 2019-08-20T15:19:40.357591+00:00 omnfrmo10 kernel: [683271.192825] usb
>> 7-1.1.3: Manufacturer: Digi International
>> 2019-08-20T15:19:40.357593+00:00 omnfrmo10 kernel: [683271.192827] usb
>> 7-1.1.3: SerialNumber: E63966100-2
>> 2019-08-20T15:19:40.513702+00:00 omnfrmo10 kernel: [683271.349103] usb
>> 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB8
>> 2019-08-20T15:19:40.513725+00:00 omnfrmo10 kernel: [683271.349311] usb
>> 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB9
>> 2019-08-20T15:19:40.537138+00:00 omnfrmo10 mtp-probe: checking bus 7,
>> device 90: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.3"
>> 2019-08-20T15:19:40.601754+00:00 omnfrmo10 kernel: [683271.433389] usb
>> 7-1.1.4: new full-speed USB device number 92 using uhci_hcd
>> 2019-08-20T15:19:40.601794+00:00 omnfrmo10 kernel: [683271.433631] usb
>> 7-1.2.3: New USB device found, idVendor=1608, idProduct=0247
>> 2019-08-20T15:19:40.601798+00:00 omnfrmo10 kernel: [683271.433634] usb
>> 7-1.2.3: New USB device strings: Mfr=1, Produc
>>
>>
>> I did some experiments (changing cables etc) but always the same. But when
>> tested with a windows system it worked all fine.
>> later i used a single port USB->Serial and all worked as expected.
>>
>> I tested with: Opensuse 15.1 on a DELL latitude E5400
>>
>> uname -a
>> Linux omnfrmo10 4.12.14-lp151.28.10-vanilla #1 SMP Sat Jul 13 17:59:31 UTC
>> 2019 (0ab03b7) x86_64 x86_64 x86_64 GNU/Linux
>>
>> I would like to improve the situation, does anyone has that device ? any hints
>> what to look at ?
>>
>> please reply direct, i am not member of this list.
>>
>> re,
>>  wh
>>
>>
>>
>>
>>
>>
>>
> 

^ permalink raw reply	[flat|nested] 8+ messages in thread

* problems with Edgeport/416
@ 2019-08-21 11:17 walter harms
  2019-08-21 11:43 ` AW: " Schmid, Carsten
  0 siblings, 1 reply; 8+ messages in thread
From: walter harms @ 2019-08-21 11:17 UTC (permalink / raw)
  To: linux-usb; +Cc: greg

Hello List,
does some use linux with an Edgeport/416 ?

I have a strange problem. the device is resetting soon
after i started using it (but not immediately).
I do not see a kernel OOPS but a common pattern is:

2019-08-20T15:19:39.825812+00:00 omnfrmo10 kernel: [683270.658623] usb 7-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:39.825818+00:00 omnfrmo10 kernel: [683270.658626] usb 7-1.1.2: Product: Edgeport/416
2019-08-20T15:19:39.825821+00:00 omnfrmo10 kernel: [683270.658628] usb 7-1.1.2: Manufacturer: Digi International
2019-08-20T15:19:39.825823+00:00 omnfrmo10 kernel: [683270.658630] usb 7-1.1.2: SerialNumber: E63966100-1
2019-08-20T15:19:39.985571+00:00 omnfrmo10 kernel: [683270.817909] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB4
2019-08-20T15:19:39.985594+00:00 omnfrmo10 kernel: [683270.818132] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB5
2019-08-20T15:19:40.007943+00:00 omnfrmo10 mtp-probe: checking bus 7, device 88: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.2"
2019-08-20T15:19:40.053750+00:00 omnfrmo10 kernel: [683270.885626] usb 7-1.2.2: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.053791+00:00 omnfrmo10 kernel: [683270.885630] usb 7-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:40.053797+00:00 omnfrmo10 kernel: [683270.885633] usb 7-1.2.2: Product: Edgeport/416
2019-08-20T15:19:40.053800+00:00 omnfrmo10 kernel: [683270.885635] usb 7-1.2.2: Manufacturer: Digi International
2019-08-20T15:19:40.053803+00:00 omnfrmo10 kernel: [683270.885637] usb 7-1.2.2: SerialNumber: E63966100-5
2019-08-20T15:19:40.065569+00:00 omnfrmo10 kernel: [683270.897406] usb 7-1.1.3: new full-speed USB device number 90 using uhci_hcd
2019-08-20T15:19:40.213569+00:00 omnfrmo10 kernel: [683271.046316] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB6
2019-08-20T15:19:40.213594+00:00 omnfrmo10 kernel: [683271.046782] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB7
2019-08-20T15:19:40.242034+00:00 omnfrmo10 mtp-probe: checking bus 7, device 89: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.2/7-1.2.2"
2019-08-20T15:19:40.301578+00:00 omnfrmo10 kernel: [683271.133380] usb 7-1.2.3: new full-speed USB device number 91 using uhci_hcd
2019-08-20T15:19:40.357559+00:00 omnfrmo10 kernel: [683271.192815] usb 7-1.1.3: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.357584+00:00 omnfrmo10 kernel: [683271.192820] usb 7-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:40.357588+00:00 omnfrmo10 kernel: [683271.192822] usb 7-1.1.3: Product: Edgeport/416
2019-08-20T15:19:40.357591+00:00 omnfrmo10 kernel: [683271.192825] usb 7-1.1.3: Manufacturer: Digi International
2019-08-20T15:19:40.357593+00:00 omnfrmo10 kernel: [683271.192827] usb 7-1.1.3: SerialNumber: E63966100-2
2019-08-20T15:19:40.513702+00:00 omnfrmo10 kernel: [683271.349103] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB8
2019-08-20T15:19:40.513725+00:00 omnfrmo10 kernel: [683271.349311] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB9
2019-08-20T15:19:40.537138+00:00 omnfrmo10 mtp-probe: checking bus 7, device 90: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.3"
2019-08-20T15:19:40.601754+00:00 omnfrmo10 kernel: [683271.433389] usb 7-1.1.4: new full-speed USB device number 92 using uhci_hcd
2019-08-20T15:19:40.601794+00:00 omnfrmo10 kernel: [683271.433631] usb 7-1.2.3: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.601798+00:00 omnfrmo10 kernel: [683271.433634] usb 7-1.2.3: New USB device strings: Mfr=1, Produc


I did some experiments (changing cables etc) but always the same. But when tested with a windows system it worked all fine.
later i used a single port USB->Serial and all worked as expected.

I tested with: Opensuse 15.1 on a DELL latitude E5400

uname -a
Linux omnfrmo10 4.12.14-lp151.28.10-vanilla #1 SMP Sat Jul 13 17:59:31 UTC 2019 (0ab03b7) x86_64 x86_64 x86_64 GNU/Linux

I would like to improve the situation, does anyone has that device ? any hints what to look at ?

please reply direct, i am not member of this list.

re,
 wh









^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, back to index

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <5D5D1C8C.9080000@bfs.de>
     [not found] ` <20190821112009.GA5228@kroah.com>
     [not found]   ` <5D5D2F9E.7050805@bfs.de>
     [not found]     ` <20190821122028.GA19107@kroah.com>
2019-08-21 13:04       ` problems with Edgeport/416 walter harms
2019-08-21 13:20         ` AW: " Schmid, Carsten
2019-08-21 13:40           ` walter harms
2019-08-21 14:12             ` AW: " Schmid, Carsten
     [not found]               ` <5D5D51FF.5010400@bfs.de>
     [not found]                 ` <2ae1fb935c2041f8b0d54e311e730ba5@SVR-IES-MBX-03.mgc.mentorg.com>
2019-08-23 15:27                   ` walter harms
2019-08-21 13:36         ` Greg KH
2019-08-21 11:17 walter harms
2019-08-21 11:43 ` AW: " Schmid, Carsten
2019-08-21 12:03   ` walter harms

Linux-USB Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-usb/0 linux-usb/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-usb linux-usb/ https://lore.kernel.org/linux-usb \
		linux-usb@vger.kernel.org linux-usb@archiver.kernel.org
	public-inbox-index linux-usb


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-usb


AGPL code for this site: git clone https://public-inbox.org/ public-inbox