Good day,
I've noticed what I suspect to be a possible xHCI regression when
upgrading from kernel 3.19.51 to 4.2.0-30 generic SMP x64 which causes
various USB3.0 cameras to no longer stream data. It appears to be
limited to Intel 9 Series on-board controllers and the occasional NEC
PCIe USB3.0 host controller I come across. I've tested a slew of about a
dozen different controllers so far, and these are the only ones that are
problematic.
I don't see any warnings/errors in the kernel log output via `dmesg',
and I've sent off a very verbose run-time log to the libusb mailing
list. Is there anything further I can do, save for a physical trace, to
further diagnose this issue?
Thank you.
============================================================
Matthew Giassa
-------- Forwarded Message --------
Subject: Re: [libusb] Potential xHCI regression upgrading kernel
3.19.0-60 to 4.2.0-30
Date: Sat, 19 Mar 2016 10:25:11 -0700
From: Matthew Giassa <matthew@xxxxxxxxxx>
To: libusb Developer Mailing List <libusb-devel@xxxxxxxxxxxxxxxxxxxxx>
As a follow-up, I've pulled out a bunch of USB3.0 host controllers to
test against, and seem to only have issues with some NEC and Intel
controller.
No issues:
============================================================
* Renesas PCIe controller (latest firmware flashed to chip).
* Fresco PCIe controller.
* Intel 7 Series on-board USB3.0 controller.
Encountered issues as described in previous message:
============================================================
* Intel 9 Series on-board controller.
* NEC USB3.0 PCIe controller.
============================================================
Matthew Giassa
On 03/18/16 14:47, Matthew Giassa wrote:
Good day,
I have some Linux USB-related issues with some USB3.0 cameras that
previously worked without issue in Ubuntu (kernel 3.16.0-60 on 14.04.2,
and kernel 3.19.0-51 on 14.04.3), and suddenly everything is no longer
functional upon upgrading to kernel 4.2.0-30 on Ubuntu 14.04.4. In all
these cases, I am testing against the x64 generic SMP kernel.
I don't see any warnings in `dmesg` logs like I've seen with either xHCI
regressions or potential libusb issues in the past, and the application
being tested is a (relatively) simple example just to grab frames from a
camera: no post-processing or other components to cause the USB core
code to fail. The application reports that it simply isn't receiving
data from the camera after sending the appropriate control sequence. I
have attached the console debug log, and wanted to know if there are any
glaring red flags that would point out if it's a kernel regression,
hidden bug in code I'm working on, or something else entirely. Thank
you, by the way.
============================================================
Matthew Giassa
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
libusb-devel mailing list
libusb-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/libusb-devel
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
libusb-devel mailing list
libusb-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/libusb-devel
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
