lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 4 Apr 2017 12:03:43 -0700
From:   John Stultz <>
To:     Felipe Balbi <>
Cc:     Minas Harutyunyan <>,
        John Youn <>,
        lkml <>,
        YongQin Liu <>,
        "" <>
Subject: Re: dwc2_hc_chhltd_intr_dma - ChHltd set errors?

On Tue, Apr 4, 2017 at 12:38 AM, Felipe Balbi
<> wrote:
> Hi,
> Minas Harutyunyan <> 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.

Thanks for the extra details! I didn't have DEBUG_FS built in, so this
helped clue me in.

Attached are dmesg including the issue and the regdump.

I did notice when cating the regdump file, I saw:
dwc2 f72c0000.usb: Mode Mismatch Interrupt: currently in Host mode
twice. (You'll see it 4 times in the dmesg around 1077 as I cat'ed
regdump again to verify it wasn't just chance).

Let me know if there is anything else you need!


Download attachment "hikey-usb.dmesg" of type "application/octet-stream" (57630 bytes)

Download attachment "hikey-usb.regdump" of type "application/octet-stream" (7547 bytes)

Powered by blists - more mailing lists