Linux-USB Archive on lore.kernel.org
 help / color / Atom feed
From: walter harms <wharms@bfs.de>
To: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"greg@kroah.com" <greg@kroah.com>
Subject: Re: problems with Edgeport/416
Date: Wed, 21 Aug 2019 14:03:54 +0200
Message-ID: <5D5D332A.3010504@bfs.de> (raw)
In-Reply-To: <741cf63f72e443ba9158c9c123fcccc7@SVR-IES-MBX-03.mgc.mentorg.com>



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
>>
>>
>>
>>
>>
>>
>>
> 

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 11:17 walter harms
2019-08-21 11:43 ` AW: " Schmid, Carsten
2019-08-21 12:03   ` walter harms [this message]
2019-08-21 12:17     ` Schmid, Carsten
     [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       ` 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

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5D5D332A.3010504@bfs.de \
    --to=wharms@bfs.de \
    --cc=Carsten_Schmid@mentor.com \
    --cc=greg@kroah.com \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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

Example config snippet for mirrors

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