Linux Input/HID development
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	USB list <linux-usb@vger.kernel.org>,
	linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [-next regression] USB keyboard stops working occasionally
Date: Mon, 28 May 2012 17:41:47 +0200	[thread overview]
Message-ID: <4FC39CBB.3040204@suse.cz> (raw)
In-Reply-To: <20120519223903.GA12572@kroah.com>

On 05/20/2012 12:39 AM, Greg Kroah-Hartman wrote:
> On Sun, May 20, 2012 at 12:17:29AM +0200, Jiri Slaby wrote:
>> Hi,
>>
>> sometimes, in the middle of writing, my USB HID keyboard stops sending
>> interrupts (no changes in /proc/interrupts). I have to hit a key on
>> another USB interface of that keyboard to resurrect the other. It
>> happens once or twice a day. It happens with -next since around Friday 4th.
>>
>> I tried to bisect it a bit (three or four times because of fuzz) in the
>> past 3 weeks and my suspect number one is currently:
>> commit 3d9545cc375d117554a9b35dfddadf9189c62775
>> Author: Alan Stern <stern@rowland.harvard.edu>
>> Date:   Mon Apr 23 13:54:36 2012 -0400
>>
>>     EHCI: maintain the ehci->command value properly
>>
>> ===
>>
>> I'm currently running on -next 20120518 with that commit reverted for
>> one whole day and the issue seems to be gone.
>>
>> Could you take a look and double-check that commit? (Or do you have any
>> other ideas where to take a look?)
> 
> Yes, we realized this a few days ago, and I committed a fix for this a
> few hours ago to the usb-next tree, and should show up in the next -next
> release.
> 
> I've included the patch below that should fix this problem, please let
> me know if it doesn't for you.

FWIW after running the kernel a couple of days without a glitch I can
conclude that it is fixed now.

thanks,
-- 
js
suse labs


      reply	other threads:[~2012-05-28 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-19 22:17 [-next regression] USB keyboard stops working occasionally Jiri Slaby
     [not found] ` <4FB81BF9.7040705-AlSwsSmVLrQ@public.gmane.org>
2012-05-19 22:39   ` Greg Kroah-Hartman
2012-05-28 15:41     ` Jiri Slaby [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=4FC39CBB.3040204@suse.cz \
    --to=jslaby@suse.cz \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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