From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] FL1009: xHCI host not responding to stop endpoint command.
Date: Tue, 18 Feb 2014 22:24:34 +0100 [thread overview]
Message-ID: <20140218222434.7e447b80@skate> (raw)
In-Reply-To: <87ppmk2lbs.fsf@natisbad.org>
Dear Arnaud Ebalard,
On Tue, 18 Feb 2014 21:54:31 +0100, Arnaud Ebalard wrote:
> > I finally got some idea: your kernel 3.13-rc7 lacks a very important
> > fix we did in the irqchip driver MSI handling. You really need to have
> > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/irqchip/irq-armada-370-xp.c?id=c7f7bd4a136e4b02dd2a66bf95aec545bd93e8db
> > applied to get proper MSI behavior. Without this patch, there is a race
> > condition, and some MSI interrupts might be lost.
> >
> > This commit was merged in v3.14-rc2, and backported to 3.13 and
> > previous stable releases.
> >
> > Can you test after applying this commit?
>
> Just to be sure, I compiled a 3.13 w/ PCI_MSI enabled and w/o the fix:
> it failed as usual. Then, I just applied the fix on top of it and tested
> again: I was unable to make it fail, i.e. this oneline fixes the issue.
Cool!
> Sarah, I guess this also validates the fact that FL1009 has good MSI
> support ;-)
>
> Thanks for the time you both spent. Let's close the case.
You're welcome. Sorry for having realized so late from where the
problem could be coming from, and that it was in fact already fixed.
Thanks to you for reporting and investigating the issue in the first
place!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-02-18 21:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 20:13 [BUG] FL1009: xHCI host not responding to stop endpoint command Arnaud Ebalard
2014-01-12 21:36 ` Arnaud Ebalard
2014-01-14 17:07 ` Sarah Sharp
2014-01-14 18:11 ` Bjørn Mork
2014-01-14 21:54 ` Arnaud Ebalard
2014-01-15 9:59 ` David Laight
2014-01-15 19:04 ` Arnaud Ebalard
2014-01-16 18:50 ` Sarah Sharp
2014-01-17 6:25 ` Arnaud Ebalard
2014-01-17 8:31 ` Bjørn Mork
2014-01-17 20:54 ` Sarah Sharp
2014-01-18 21:49 ` Arnaud Ebalard
2014-01-21 21:17 ` Sarah Sharp
2014-01-22 22:23 ` Arnaud Ebalard
2014-01-22 22:26 ` Jason Cooper
2014-01-22 22:43 ` Arnaud Ebalard
2014-01-22 23:56 ` Sarah Sharp
2014-01-23 8:24 ` Arnaud Ebalard
2014-01-23 11:09 ` Willy Tarreau
2014-01-27 22:20 ` Arnaud Ebalard
2014-01-26 13:30 ` Thomas Petazzoni
2014-01-27 18:36 ` Arnaud Ebalard
2014-02-10 18:57 ` Arnaud Ebalard
2014-02-14 0:09 ` Sarah Sharp
2014-02-14 8:26 ` Thomas Petazzoni
2014-02-18 13:10 ` Thomas Petazzoni
2014-02-18 20:54 ` Arnaud Ebalard
2014-02-18 21:24 ` Thomas Petazzoni [this message]
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=20140218222434.7e447b80@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).