dwc_otg problem

[Hans Petter Selasky]

On 12/14/16 02:25, Ganbold Tsagaankhuu wrote:
> On Wed, Dec 14, 2016 at 3:06 AM, Hans Petter Selasky <hps at selasky.org>
> wrote:
>
>> On 12/13/16 10:01, Ganbold Tsagaankhuu wrote:
>>
>>> usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
>>> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
>>> USB_ERR_TIMEOUT
>>> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
>>> ignored)
>>> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
>>> USB_ERR_TIMEOUT
>>> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
>>> ignored)
>>> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
>>> USB_ERR_TIMEOUT
>>> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
>>> ignored)
>>> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
>>> USB_ERR_TIMEOUT
>>> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
>>> ignored)
>>> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
>>> USB_ERR_TIMEOUT
>>> ugen1.2: <Unknown > at usbus1 (disconnected)
>>> uhub_reattach_port: could not allocate new device
>>> ...
>>>
>>
>> Hi,
>>
>> This might look like a DWC OTG IRQ problem. Can you check "vmstat -i" ?
>
>
> I can't boot further than those messages.
>
> Ganbold

Hi,

You can possibly enable "hw.usb.dwc_otg.debug=16" from the loader.

I suspect it is a problem with the FDT, that the IRQ is incorrectly mapped.

--HPS