public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	USB list <linux-usb@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Subject:  [v3.8 Regression]  UHCI: OHCI: implement new semantics for URB_ISO_ASAP
Date: Mon, 24 Jun 2013 12:35:32 -0400	[thread overview]
Message-ID: <51C87554.8010503@canonical.com> (raw)

Hi Alan,

A bug was opened against the Ubuntu distro[0].  It is believed that the
following commits introduced the regression:

commit c44b225077bb1fb25ed5cd5c4f226897b91bedd4
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Mon Oct 1 10:32:09 2012 -0400

    UHCI: implement new semantics for URB_ISO_ASAP

commit 6a41b4d3fe8cd4cc95181516fc6fba7b1747a27c
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Mon Oct 1 10:32:15 2012 -0400

    OHCI: implement new semantics for URB_ISO_ASAP




The regression was introduced as of v3.8-rc1. 

I see the following commit was created to address a similar issue to this:

commit e1944017839d7dfbf7329fac4bdec8b4050edf5e
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Tue May 14 13:57:19 2013 -0400

    USB: fix latency in uhci-hcd and ohci-hcd

I created a test kernel with commit
e1944017839d7dfbf7329fac4bdec8b4050edf5e.  However, folks affected state
this bug still exists with commit e194401.  It is also reported that
this bug exists in the latest Mainline kernel.

I see that you are the author of these patches, so I wanted to get your
opinion on the issue.

Thanks,

Joe

[0] http://pad.lv/1191603


                 reply	other threads:[~2013-06-24 16:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51C87554.8010503@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox