From: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
To: "wharms@bfs.de" <wharms@bfs.de>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"greg@kroah.com" <greg@kroah.com>
Subject: AW: problems with Edgeport/416
Date: Wed, 21 Aug 2019 12:17:31 +0000 [thread overview]
Message-ID: <2a533cdf9743457bb4998b0409f28f3d@SVR-IES-MBX-03.mgc.mentorg.com> (raw)
In-Reply-To: <5D5D332A.3010504@bfs.de>
> > (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 ?
>
From the log of your kernel messages, it seems that uhci_hcd takes over the transport.
So you should do
echo -n 'module uhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control
echo -n 'module usbcore =p' > /sys/kernel/debug/dynamic_debug/control
> I did not know about dynamic-debug, fortunately linux drivers simply work
> these days :)
Helps a bit to better understand what goes wrong.
If you look into dmesg after enabling the dyndeb messages, you should see much more than
USB connect messages.
But be aware that there are quite a lot of messages that appear in dmesg.
Best is to enable the dyndbg, then immediately plug in the device, and
after a few seconds (5 seconds or so) you should do a
dmesg > mylog.txt
Then you have the dmesg captured into the text file mylog.txt and you have time to check it.
Check for USB error messages in this file.
Best regards
Carsten
next prev parent reply other threads:[~2019-08-21 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 11:17 problems with Edgeport/416 walter harms
2019-08-21 11:43 ` AW: " Schmid, Carsten
2019-08-21 12:03 ` walter harms
2019-08-21 12:17 ` Schmid, Carsten [this message]
[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
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=2a533cdf9743457bb4998b0409f28f3d@SVR-IES-MBX-03.mgc.mentorg.com \
--to=carsten_schmid@mentor.com \
--cc=greg@kroah.com \
--cc=linux-usb@vger.kernel.org \
--cc=wharms@bfs.de \
/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).