All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthew Giassa" <matthew@giassa.net>
To: linux-media@vger.kernel.org
Cc: "Mathias Nyman" <mathias.nyman@intel.com>, greg@kroah.com
Subject: USB xHCI regression after upgrading from kernel 3.19.0-51 to 4.2.0-34.
Date: Thu, 07 Apr 2016 08:36:43 -0700	[thread overview]
Message-ID: <20160407083643.fccade4f64c1f11ce2bc6da07fd9ab91.977bcc175f.wbe@email16.secureserver.net> (raw)

Good day,

I maintain an SDK for USB2.0 and USB3.0 U3V machine vision cameras, and
several of my customers have reported severe issues since upgrading from
kernel 3.19.0-51 (Ubuntu 14.04.3 LTS) to kernel 4.2.0-34 (Ubuntu 14.04.4
LTS). I've received helpful advice from members of the libusb and
linux-usb mailing list and development groups on how to generate useful
logs to help diagnose the issue, and have filed a bug to track this
issue at:

  https://bugzilla.kernel.org/show_bug.cgi?id=115961

It seems that with kernels newer than the 3.19 series (I've tested on
4.2.0-34, and just repeated the tests on the latest 4.5.0 release), the
cameras lock up, and cannot stream image data to the user application. I
am able to resolve the issue on 4.2.0-34 by disabling USB power
management by adding "usbcore.autosuspend=-1". On the 4.5 kernel, this
"trick" doesn't work at all, and I have no way to get the cameras to
stream data. I can do simple USB control requests to query things like
register values and serial numbers, but that's it. Asynchronous bulk
transfers never succeed.

Special Cases:
 * The issue does not occur when using USB2.0 cameras on a USB2.0 port,
regardless of the kernel in use.
 * The issues occur only on Intel 8 Series and Intel 9 Series USB3.0
host controllers with 4.x kernels.
 * Intel 10 Series host controllers have not yet been tested.
 * The issues never occur on Fresco or Renesas host controllers,
regardless of the kernel in use.
 * From visual inspection of lsusb output, the issue only appears to
happen when the U1 and U2 options are available to the device.

I would like to request assistance with diagnosing and resolving the
issue, as it requires our customers to either not use Intel host
controllers, or sticking to older kernel releases.

Thank you for your time and assistance.

============================================================
Matthew Giassa, MASc, BASc, EIT
Security and Embedded Systems Specialist
linkedin: https://ca.linkedin.com/in/giassa
e-mail:   matthew@giassa.net
website:  www.giassa.net


             reply	other threads:[~2016-04-07 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 15:36 Matthew Giassa [this message]
2016-04-08  8:51 ` USB xHCI regression after upgrading from kernel 3.19.0-51 to 4.2.0-34 Hans de Goede
2016-04-08 14:26   ` Greg KH

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=20160407083643.fccade4f64c1f11ce2bc6da07fd9ab91.977bcc175f.wbe@email16.secureserver.net \
    --to=matthew@giassa.net \
    --cc=greg@kroah.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.