public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Phil Turmel <philip@turmel.org>
Cc: Guillaume Chazarain <guichaz@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org,
	"Greg Kroah-Hartman" <gregkh@suse.de>,
	Alan Stern <stern@rowland.harvard.edu>,
	Oliver Neukum <oliver@neukum.org>, Alan Ott <alan@signal11.us>,
	linux-usb@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [BUG, Regression, bisected] USB mouse causes bug on 1st insert, ignored on 2nd insert, lsusb stuck at usbdev_open
Date: Mon, 20 Sep 2010 21:35:41 +0200	[thread overview]
Message-ID: <201009202135.41833.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <4C96B9DB.8030403@turmel.org>

On poniedziałek, 20 września 2010 o 03:33:15 Phil Turmel wrote:
> A new regression was introduced between -rc3 and -rc4:
> 
> The USB mouse I use with my laptop is causing a BUG when inserted.  It
> works at that point, but if removed and re-inserted, it is ignored.  Also,
> after the 2nd insert, other USB devices (like my thumb drive) are also
> ignored.
> 

I created a Bugzilla entry at 
https://bugzilla.kernel.org/show_bug.cgi?id=18892
for your bug report, please add your address to the CC list in there, thanks!

-- 
Maciej Rutecki
http://www.maciek.unixy.pl

      parent reply	other threads:[~2010-09-20 19:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20  1:33 [BUG, Regression, bisected] USB mouse causes bug on 1st insert, ignored on 2nd insert, lsusb stuck at usbdev_open Phil Turmel
2010-09-20  9:43 ` Guillaume Chazarain
2010-09-20 10:47   ` Phil Turmel
2010-09-20 12:42   ` Jiri Kosina
2010-09-20 13:19     ` Phil Turmel
2010-09-20 13:25       ` Jiri Kosina
2010-09-20 13:56         ` Mat
2010-09-20 15:10           ` Jiri Kosina
2010-09-20 17:05             ` Mat
2010-09-20 17:40             ` Phil Turmel
2010-09-21 12:31               ` Jiri Kosina
2010-09-21 13:57                 ` Jiri Kosina
2010-09-21 14:48                   ` Heinz Diehl
2010-09-21 14:55                     ` Jiri Kosina
2010-09-21 14:30                 ` Alan Stern
2010-09-21 14:40                   ` Jiri Kosina
2010-09-21 14:42                     ` Phil Turmel
2010-09-21 14:54                   ` Phil Turmel
2010-09-21 16:08                     ` Gabriel C
2010-09-22  9:47                       ` Mat
2010-09-24 16:46                         ` Greg KH
2010-09-21 16:50                   ` Greg KH
2010-09-21 16:55                     ` Jiri Kosina
2010-09-21 17:07                       ` Greg KH
2010-09-21 17:14                         ` Jiri Kosina
2010-09-20 20:55             ` Alan Stern
2010-09-20 22:48               ` Jiri Kosina
2010-09-21  0:41                 ` Andreas Bombe
2010-09-20 14:11         ` Phil Turmel
2010-09-20 19:35 ` Maciej Rutecki [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=201009202135.41833.maciej.rutecki@gmail.com \
    --to=maciej.rutecki@gmail.com \
    --cc=alan@signal11.us \
    --cc=gregkh@suse.de \
    --cc=guichaz@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=philip@turmel.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