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/com
Hi Thomas,
Thomas Petazzoni writes:
> Dear Arnaud Ebalard,
>
> On Sat, 18 Jan 2014 22:49:17 +0100, Arnaud Ebalard wrote:
>
>> I started suspecting the introduction of MSI support in Marvell PCIe
>> host controller driver (FL1009 is on the PCIe bus) and compiled a
>> a 3.13.0-rc8 w/ CONFIG_PCI_MS
Dear Arnaud Ebalard,
On Sat, 18 Jan 2014 22:49:17 +0100, Arnaud Ebalard wrote:
> I started suspecting the introduction of MSI support in Marvell PCIe
> host controller driver (FL1009 is on the PCIe bus) and compiled a
> a 3.13.0-rc8 w/ CONFIG_PCI_MSI disabled (it was enabled in all my
> previous
Sarah, Arnaud,
On Thu, 13 Feb 2014 16:09:10 -0800, Sarah Sharp wrote:
> > Unless you have some objections or some positive feedback from Fresco
> > Logic people, can you queue your quirks for FL1009 for 3.14-rc* and
> > -stable? Note that I am just asking, i.e. if you want to wait a bit
> > more,
On Mon, Feb 10, 2014 at 07:57:42PM +0100, Arnaud Ebalard wrote:
> Sarah Sharp writes:
>
> > On Wed, Jan 22, 2014 at 11:43:16PM +0100, Arnaud Ebalard wrote:
> >> f5182b4155b9d686c5540a6822486400e34ddd98 "xhci: Disable MSI for some
> >> Fresco Logic hosts."
> >>
> >> Technically, this is not per
Hi Sarah,
Sarah Sharp writes:
> On Wed, Jan 22, 2014 at 11:43:16PM +0100, Arnaud Ebalard wrote:
>> Hi Jason,
>>
>> Jason Cooper writes:
>>
>> > On Wed, Jan 22, 2014 at 11:23:23PM +0100, Arnaud Ebalard wrote:
>> >> With the patch applied on top of 3.13.0 kernel recompiled w/
>> >> CONFIG_PCI_M
Hi Willy,
Willy Tarreau writes:
>> > I don't know if it should have included FL1009, it was just a guess,
>> > based on the fact that the 0x1000 and 0x1400 devices did need MSI
>> > disabled. I can attempt to ask the Fresco Logic folks I know, but I'm
>> > not sure if/when I'll get a response b
Hi Thomas and Sarah,
Thomas Petazzoni writes:
> On Thu, 23 Jan 2014 09:24:41 +0100, Arnaud Ebalard wrote:
>
>> The various Armada-based devices I have are NAS which do not have PCIe
>> slots to plug additional devices (everything is soldered). I don't know
>> which device Thomas used for its tes
Dear Arnaud Ebalard,
On Thu, 23 Jan 2014 09:24:41 +0100, Arnaud Ebalard wrote:
> The various Armada-based devices I have are NAS which do not have PCIe
> slots to plug additional devices (everything is soldered). I don't know
> which device Thomas used for its tests. Just in case, I also added Wi
On Thu, Jan 23, 2014 at 09:24:41AM +0100, Arnaud Ebalard wrote:
> Hi Sarah,
>
> Sarah Sharp writes:
>
> >> > Can you pinpoint the commit that introduced the regression?
> >>
> >> f5182b4155b9d686c5540a6822486400e34ddd98 "xhci: Disable MSI for some
> >> Fresco Logic hosts."
> >>
> >> Technical
Hi Sarah,
Sarah Sharp writes:
>> > Can you pinpoint the commit that introduced the regression?
>>
>> f5182b4155b9d686c5540a6822486400e34ddd98 "xhci: Disable MSI for some Fresco
>> Logic hosts."
>>
>> Technically, this is not per se the commit which introduced the
>> regression but the one tha
On Wed, Jan 22, 2014 at 11:43:16PM +0100, Arnaud Ebalard wrote:
> Hi Jason,
>
> Jason Cooper writes:
>
> > On Wed, Jan 22, 2014 at 11:23:23PM +0100, Arnaud Ebalard wrote:
> >> With the patch applied on top of 3.13.0 kernel recompiled w/
> >> CONFIG_PCI_MSI enabled, I cannot reproduce the bug. I
Hi Jason,
Jason Cooper writes:
> On Wed, Jan 22, 2014 at 11:23:23PM +0100, Arnaud Ebalard wrote:
>> With the patch applied on top of 3.13.0 kernel recompiled w/
>> CONFIG_PCI_MSI enabled, I cannot reproduce the bug. I guess
>> you can add my:
>>
>> Reported-and-tested-By: Arnaud Ebalard
>>
>
On Wed, Jan 22, 2014 at 11:23:23PM +0100, Arnaud Ebalard wrote:
> With the patch applied on top of 3.13.0 kernel recompiled w/
> CONFIG_PCI_MSI enabled, I cannot reproduce the bug. I guess
> you can add my:
>
> Reported-and-tested-By: Arnaud Ebalard
>
> Since you'll have to push the patch to -s
Hi Sarah,
Sarah Sharp writes:
> On Sat, Jan 18, 2014 at 10:49:17PM +0100, Arnaud Ebalard wrote:
>> Hi,
>>
>> I have added Thomas in the recipients, because I guess he may be of some
>> help debugging the issue further. Thomas, the beginning of the thread is
>> here: http://thread.gmane.org/gman
On Sat, Jan 18, 2014 at 10:49:17PM +0100, Arnaud Ebalard wrote:
> Hi,
>
> I have added Thomas in the recipients, because I guess he may be of some
> help debugging the issue further. Thomas, the beginning of the thread is
> here: http://thread.gmane.org/gmane.linux.usb.general/101531
...
> I sta
Hi,
I have added Thomas in the recipients, because I guess he may be of some
help debugging the issue further. Thomas, the beginning of the thread is
here: http://thread.gmane.org/gmane.linux.usb.general/101531
Sarah Sharp writes:
>> >>> I am slowly starting to see a bisect session coming ;-)
>
On Fri, Jan 17, 2014 at 09:31:16AM +0100, Bjørn Mork wrote:
> a...@natisbad.org (Arnaud Ebalard) writes:
> > Sarah Sharp writes:
> >
> >>> ... AFAICT, this is exactly what commit 35773dac5f86 does and reverting
> >>> it does not help. If I am mistaken, can you point which part you want me
> >>> to
a...@natisbad.org (Arnaud Ebalard) writes:
> Sarah Sharp writes:
>
>>> ... AFAICT, this is exactly what commit 35773dac5f86 does and reverting
>>> it does not help. If I am mistaken, can you point which part you want me
>>> to remove in the code to test?
>>>
>>> I am slowly starting to see a bise
Hi,
Sarah Sharp writes:
>> ... AFAICT, this is exactly what commit 35773dac5f86 does and reverting
>> it does not help. If I am mistaken, can you point which part you want me
>> to remove in the code to test?
>>
>> I am slowly starting to see a bisect session coming ;-)
>
> Try reverting commit
On Wed, Jan 15, 2014 at 08:04:45PM +0100, Arnaud Ebalard wrote:
> Hi David,
>
> David Laight writes:
>
> >> I tried current 3.13.0-rc8 w/ 35773dac5f86 reverted and the result is
> >> the same:
> >
> > That patch only affects an error code and stops the fs code retrying
> > for ever.
>
> Are you
Hi David,
David Laight writes:
>> I tried current 3.13.0-rc8 w/ 35773dac5f86 reverted and the result is
>> the same:
>
> That patch only affects an error code and stops the fs code retrying
> for ever.
Are you sure? ...
> Does everything work if you comment out the code in xhci-ring.c that add
From: Arnaud Ebalard
> Sent: 14 January 2014 21:54
> To: Sarah Sharp
> Cc: linux-usb@vger.kernel.org; linux-arm-ker...@lists.infradead.org; Bjørn
> Mork
> Subject: Re: [BUG] FL1009: xHCI host not responding to stop endpoint command.
>
> Hi Sarah,
>
> Sarah Sharp wr
Hi Sarah,
Sarah Sharp writes:
>> I can add the following:
>>
>> 2) I just tested the copy of the small files using the ICY DOCK
>> MB981U3S-1S connected to my ReadyNAS 102 *on a 3.11.7 kernel*
>> and it completed successfully.
>
> Please try a 3.13-rc7 kernel after running `git revert 35773dac
Sarah Sharp writes:
> On Sun, Jan 12, 2014 at 10:36:56PM +0100, Arnaud Ebalard wrote:
>
>> a...@natisbad.org (Arnaud Ebalard) writes:
>>
>> 2) on current 3.13.0-rc7 kernel (w/ Bjørn patch applied just in case), I
>
> Which patch are you referring to?
I wondered about that too at first :-)
But l
On Sun, Jan 12, 2014 at 10:36:56PM +0100, Arnaud Ebalard wrote:
> Hi,
>
> a...@natisbad.org (Arnaud Ebalard) writes:
>
> > Both with a LaCie 2.5" USB 3.0 Rugged Mini disk (powered by the port)
> > and a 3.5" SATA disk connected via an ICY DOCK MB981U3S-1S dock station
> > (external power), I can
Hi,
a...@natisbad.org (Arnaud Ebalard) writes:
> Both with a LaCie 2.5" USB 3.0 Rugged Mini disk (powered by the port)
> and a 3.5" SATA disk connected via an ICY DOCK MB981U3S-1S dock station
> (external power), I can transfer huge files w/o issue but I get the
> following when transferring smal
27 matches
Mail list logo
