On Tue, Feb 11, 2014 at 06:11:09PM +0100, Andreas Cadhalpun wrote:
> Hi,
>
> thanks for looking into the issue.
>
> On 11.02.2014 17:40, Sarah Sharp wrote:
> >On Sat, Feb 08, 2014 at 03:56:31AM +, Ben Hutchings wrote:
> >>For the benefit of other developers, tha
tried reverting commit
9df89d85b407690afa46ddfbccc80bec6869971d "usbcore: set lpm_capable field
for LPM capable root hubs"? It enables USB 3.0 Link PM for non-Intel
host controllers, which is not what I intended, and could cause issues
with other host controllers. A patch to revert that wa
anks for letting me know, Johannes. The patch is queued for 3.14,
and won't land in the stable kernels until after 3.14-rc1 (in a couple
weeks).
Sarah Sharp
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140120202720.GH5545@xanatos
Dan, can you test this patch, on top of the other patch that Ben sent?
There's directions for building a custom kernel here, if you need it:
http://kernelnewbies.org/KernelBuild
I suggest either getting the Debian kernel source and patching that, or
patching 3.12.6 or later.
Sarah Sha
4k page.
>
> Whether anything regularly exceeds 255 fragments is a another matter.
If so, yes, changing the segment size makes sense. TRBS_PER_SEGMENT
could be increased to 256. I'm not sure if we should switch to using
dma_alloc_coherent instead of a DMA pool. Some systems could be
by a wall-wort.
So introducing a USB 2.0 hub may fix the transfer errors caused by the
host.
BTW, do these Ivy Bridge systems have any (blue) USB 3.0 ports? If so,
does your mouse and keyboard work under those ports?
Sarah Sharp
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.d
Thanks Guillaume! No rush, I just wanted to make sure I hadn't dropped
the ball on a bug report.
Sarah Sharp
On Fri, May 25, 2012 at 12:42:31AM +0200, Guillaume Jaouen wrote:
> Hi,
>
> I'm really sorry but I had no time yet for tracking this bug.
>
> As requested, I w
On Sun, May 20, 2012 at 03:50:29AM -0500, Jonathan Nieder wrote:
> In February, Sarah Sharp wrote:
> > On Mon, Feb 27, 2012 at 08:18:13PM +0100, guillaume.jao...@free.fr wrote:
> [...]
> > I can't be sure that your host controller is the thing that's broken
> > u
#x27;ll really want to be
running 3.3, since that cleaned up a lot of the xHCI driver debugging,
and the log file will be much smaller.
It's possible, although not likely, that we're over writing the link TRB
on the command ring and causing the host controller to step off into
lala land and access bad memory. My other theory is that your express
card is just broken and can't handle the throughput. Or perhaps it's an
early prototype that made it out into the market without having good
transfer error support.
Sarah Sharp
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120228201901.GG6078@xanatos
On Wed, Dec 28, 2011 at 06:11:14PM +0100, Mathieu Malaterre wrote:
> On Thu, Dec 22, 2011 at 8:52 PM, Sarah Sharp
> wrote:
> > On Thu, Dec 22, 2011 at 04:18:56PM +0100, Mathieu Malaterre wrote:
> >> On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder
> >> wrote:
&
nf, run
> >
> > update-initramfs -u -k all
> >
> > and reboot to try again without USB 3.0 support. If we're very
> > lucky, this will work around the problem. In that case, please
> > write a summary of the problem to upstream
> >
e may need to be backported.
Can you add this bug (or a link to the debian bug) to the kernel.org
bugzilla? I'm trying to get all my xHCI-related bug reports and feature
requests there.
Sarah Sharp
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100607162007.gb8...@xanatos
12 matches
Mail list logo
