linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: "Sébastien Dinot" <sebastien.dinot@free.fr>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
	689368@bugs.debian.org
Subject: Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Date: Thu, 4 Oct 2012 15:59:21 -0700	[thread overview]
Message-ID: <20121004225921.GA25847@xanatos> (raw)
In-Reply-To: <20121004213606.GA8409@dinot.net>

On Thu, Oct 04, 2012 at 11:36:06PM +0200, Sébastien Dinot wrote:
> Alan Stern a écrit :
> > The log file shows lots and lots of low-level communication errors.
> > They could be caused by bad cabling or by bad USB hardware in your
> > computer. It's unlikely that they were caused by the mouse or
> > keyboard, because the log shows errors for both of them starting at
> > exactly the same times.
> 
> In my humble opinion, this issue is not caused by a bad USB hardware
> because I am encountering it with two different motherboards (MSI
> Z77A-G43 and ASUS P8Z77-V LX), both with an uptodate BIOS.
> 
> May be it is caused by a bad cabling but my mouse and my keyboard worked
> fine with my previous PC. They are connected to USB2 ports in both
> cases. But to clear up this point, I will try new mouse and keyboard.
> 
> A last question: if it is a cable failure, why does it disappear
> temporarily when I unload then reload the module? I do not have deep
> experience and knowledge of hardware, may be there is a rational
> explanation to it.
> 
> > You could try getting a USB-2 hub and attaching your mouse and
> > keyboard through the hub. That might help ... or it might not.
> 
> Sorry, I do not understand the aim of this operation. Could you explain
> me it?

Sometimes USB 2.0 hubs can handle more electrical noise from the host
controller, especially if they are externally powered 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20121004225921.GA25847@xanatos

  reply	other threads:[~2012-10-04 22:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121004194347.GB6927@dinot.net>
     [not found] ` <20121004194347.GB6927-RqwYBe9jBbFeoWH0uzbU5w@public.gmane.org>
2012-10-04 20:59   ` Mouse and keyboard freeze on Ivy Bridge platform Alan Stern
2012-10-04 21:36     ` Bug#689368: " Sébastien Dinot
2012-10-04 22:59       ` Sarah Sharp [this message]
2012-10-05 14:23       ` Alan Stern
2012-10-17 20:13         ` Sébastien Dinot
2012-10-17 20:54           ` Jonathan Nieder
     [not found]             ` <20121017205401.GF12456-fcEM2ccDkbL2nhBuCrrZHw@public.gmane.org>
2012-10-17 21:12               ` Sébastien Dinot

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=20121004225921.GA25847@xanatos \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=689368@bugs.debian.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sebastien.dinot@free.fr \
    --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;
as well as URLs for NNTP newsgroup(s).