stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Felipe Balbi <balbi@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<linux-usb@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH] Revert "usb: dwc3: gadget: drop unnecessary loop when cleaning up TRBs"
Date: Mon, 31 Aug 2015 13:50:10 -0500	[thread overview]
Message-ID: <20150831185010.GH31101@saruman.tx.rr.com> (raw)
In-Reply-To: <20150831172510.GC29811@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

Hi,

On Mon, Aug 31, 2015 at 08:25:10PM +0300, Ville Syrjälä wrote:
> On Mon, Aug 31, 2015 at 11:54:13AM -0500, Felipe Balbi wrote:
> > On Mon, Aug 31, 2015 at 07:48:28PM +0300, ville.syrjala@linux.intel.com wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > 
> > > This reverts commit 8f2c9544aba636134303105ecb164190a39dece4.
> > > 
> > > As it breaks g_ether on my Baytrail FFRD8 device. Everything starts out
> > > fine, but after a bit of data has been transferred it just stops
> > > flowing.
> > > 
> > > Note that I do get a bunch of these "NOHZ: local_softirq_pending 08"
> > > when booting the machine, but I'm not really sure if they're related
> > > to this problem.
> > 
> > I have a feeling your problem is elsewhere. We *are* completing one TRB
> > at a time. By reverting that commit you're just masking the real problem
> > and I'd rather get that one fixed.
> > 
> > How do you reproduce your issue ?
> 
> Just boot the system, it gets an IP from dnsmasq on my host, then I ssh
> into it and do something to produce a bit of console output, after which
> g_ether is dead. Eg. 'dmesg' a few times is enough to kill it.

which kernel version ? Running as USB2 or USB3 ? Have you tried
linux-next ? I just did 1000 dmesg iterations over ssh with g_ether and
saw no issues.

Can you enable dwc3 tracepoints and try again ? (use some very large
trace buffer, something around 2 or 4 MiB should be enough).

cheers

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-08-31 18:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 16:48 [PATCH] Revert "usb: dwc3: gadget: drop unnecessary loop when cleaning up TRBs" ville.syrjala
2015-08-31 16:54 ` Felipe Balbi
2015-08-31 17:25   ` Ville Syrjälä
2015-08-31 18:50     ` Felipe Balbi [this message]
2015-08-31 18:52       ` Felipe Balbi
2015-09-01 13:17       ` Ville Syrjälä
2015-09-01 13:59         ` Felipe Balbi
2015-09-01 14:39           ` Ville Syrjälä
2015-09-01 15:17             ` Felipe Balbi
2015-09-01 15:37               ` Ville Syrjälä
2015-09-07  6:56                 ` Heikki Krogerus
2015-09-28 18:56                   ` Ville Syrjälä
2015-09-02  8:09   ` Masakazu Mokuno
2015-09-02 12:29     ` Felipe Balbi
2015-10-12 18:37       ` Felipe Balbi
2015-11-06 12:48         ` Heikki Krogerus
2015-11-06 12:57           ` Heikki Krogerus
2015-11-06 13:31           ` Felipe Balbi
2015-08-31 19:21 ` Sergei Shtylyov
2015-09-01 11:40   ` Sergei Shtylyov

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=20150831185010.GH31101@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).