From: walter harms <wharms@bfs.de>
To: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: problems with Edgeport/416
Date: Fri, 23 Aug 2019 17:27:56 +0200 [thread overview]
Message-ID: <5D6005FC.1060002@bfs.de> (raw)
In-Reply-To: <2ae1fb935c2041f8b0d54e311e730ba5@SVR-IES-MBX-03.mgc.mentorg.com>
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
next prev parent reply other threads:[~2019-08-23 15:28 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
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 [this message]
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=5D6005FC.1060002@bfs.de \
--to=wharms@bfs.de \
--cc=Carsten_Schmid@mentor.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
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).