From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
John Stultz <john.stultz@linaro.org>,
Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
Cc: John Youn <John.Youn@synopsys.com>,
lkml <linux-kernel@vger.kernel.org>,
YongQin Liu <yongqin.liu@linaro.org>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: dwc2_hc_chhltd_intr_dma - ChHltd set errors?
Date: Tue, 04 Apr 2017 10:38:11 +0300 [thread overview]
Message-ID: <87inmkipwc.fsf@linux.intel.com> (raw)
In-Reply-To: <410670D7E743164D87FA6160E7907A56FD9F6F17@am04wembxb.internal.synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
Hi,
Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> writes:
>>>>>> We've noticed that when using usb ethernet adapters on HiKey, we
>>>>>> occasionally see errors like:
>>>>>>
>>>>>> dwc2 f72c0000.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set,
>>>>>> but reason is unknown
>>>>>> dwc2 f72c0000.usb: hcint 0x00000002, intsts 0x06200029
>>>>>>
>>>>>> dwc2 f72c0000.usb: dwc2_hc_chhltd_intr_dma: Channel 11 - ChHltd set,
>>>>>> but reason is unknown
>>>>>> dwc2 f72c0000.usb: hcint 0x00000002, intsts 0x04200029
>>>>>>
>>>>>> Sometimes followed up by a usb error in the driver, something like:
>>>>>> asix 1-1.2:1.0 eth0: asix_rx_fixup() Bad Header Length 0x36000807, offset 68
>>>>>>
>>>>>> Curious if you've seen any reports like this?
>>>
>>> The core version is less than 2.71a, am I right?
>>
>> So it looks like its reporting 0x4f54300a for hsotg->regs + GSNPSID
>> which looks like DWC2_CORE_REV_3_00a
>>
>>> Please send full debug log to do more investigation.
>>
>> Full dmesg, or is there special debugging you want me to enable?
>
> Full dmesg around issue.
>>
>>> Also send us regdump after connecting ethernet adapter.
>>
>> Sorry, can you clarify how to generate this?
>
> cat regdump. To locate dwc2 regdump file: cd /; find -name regdump
this won't work if his distro doesn't mount debugfs. Please give
complete instructions ;-)
# mkdir -p /d
# mount -t debugfs none /d
# cd /d
# find . -name regdump
The directory name is the same name as the dwc2 device name, AFAICT. So,
check your DTS for the name of the device.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-04-04 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 20:00 dwc2_hc_chhltd_intr_dma - ChHltd set errors? John Stultz
2017-03-31 23:04 ` John Stultz
2017-04-03 5:23 ` John Youn
2017-04-03 12:54 ` Minas Harutyunyan
2017-04-04 3:04 ` John Stultz
2017-04-04 7:18 ` Minas Harutyunyan
2017-04-04 7:38 ` Felipe Balbi [this message]
2017-04-04 19:03 ` John Stultz
2017-04-05 12:58 ` Minas Harutyunyan
[not found] ` <CALAqxLU22kn61dV7yW0+-F1b24O20nALt7462UY2Yi6ZrF_RtQ@mail.gmail.com>
2017-04-06 7:36 ` Minas Harutyunyan
2017-04-06 22:53 ` John Stultz
[not found] ` <CALAqxLU4ZK6u_QurTp1X89nD46r+3ctVzDDtsHVDq1sORhyW5w@mail.gmail.com>
2017-04-07 8:18 ` Felipe Balbi
2017-04-07 12:52 ` Minas Harutyunyan
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=87inmkipwc.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=John.Youn@synopsys.com \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=yongqin.liu@linaro.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).