From: walter harms <wharms@bfs.de>
To: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: problems with Edgeport/416
Date: Wed, 21 Aug 2019 15:40:47 +0200 [thread overview]
Message-ID: <5D5D49DF.1040800@bfs.de> (raw)
In-Reply-To: <eb4392d938654d99a3f37820b279c839@SVR-IES-MBX-03.mgc.mentorg.com>
[-- 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 --]
next prev parent reply other threads:[~2019-08-21 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2019-08-21 14:12 ` 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
Reply instructions:
You may reply publicly 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=5D5D49DF.1040800@bfs.de \
--to=wharms@bfs.de \
--cc=Carsten_Schmid@mentor.com \
--cc=gregkh@linuxfoundation.org \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).