SMSC95XX: Failed interrupt request

General discussion about anything related to Ultibo.
mark
Posts: 1185
Joined: Mon Oct 03, 2016 2:12 am
Location: Indianapolis, US

SMSC95XX: Failed interrupt request

Postby mark » Mon May 14, 2018 10:05 am

I get some of these messages every time I run this for a few hours:
https://github.com/markfirmware/bluetooth-dev/releases

Code: Select all

[ERROR] USB: Device 3: SMSC95XX: Failed interrupt request (Status = USB_STATUS_HARDWARE_ERROR)


They might occur within the time frame of a dhcp refresh, but I am not sure.

They don't seem to have any negative effect on the intended operation of the kernel.

Regards,
Mark
Ultibo - The Internet of Things that Just Work
User avatar
Ultibo
Site Admin
Posts: 1980
Joined: Sat Dec 19, 2015 3:49 am
Location: Australia

Re: SMSC95XX: Failed interrupt request

Postby Ultibo » Mon May 14, 2018 11:12 pm

mark wrote:I get some of these messages every time I run this for a few hours:
https://github.com/markfirmware/bluetooth-dev/releases

Code: Select all

[ERROR] USB: Device 3: SMSC95XX: Failed interrupt request (Status = USB_STATUS_HARDWARE_ERROR)


They might occur within the time frame of a dhcp refresh, but I am not sure.

They don't seem to have any negative effect on the intended operation of the kernel.

The interrupt endpoint is used for the link status detection which was added recently, like all interrupt endpoints it is polled (by resubmitting the request) multiple times per second and it is possible that the hardware will occasionally reject a packet.

The design allows for a failed interrupt request and simply logs the error and resubmits the request, we have noticed a similar thing happen very occasionally with certain mice and keyboards. We'll keep a note of this one to make sure it isn't a symptom of another issue.
Ultibo.org | Make something amazing
https://ultibo.org

Return to “Discussion”

Who is online

Users browsing this forum: No registered users and 0 guests