public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Bombe <aeb@debian.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>, Arnd Bergmann <arnd@arndb.de>,
	linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: OOPS in hiddev_open on connecting "Logitech MX620 Laser Cordless Mouse"
Date: Sat, 18 Sep 2010 15:36:11 +0200	[thread overview]
Message-ID: <20100918133610.GA4554@amos.infernal> (raw)
In-Reply-To: <AANLkTikOowB=8=3cnJ0QgJNfBsVeMUrkNT0E0uH2LDXL@mail.gmail.com>

On Sat, Sep 18, 2010 at 11:30:56AM +0200, Alex Riesen wrote:
> Happens with Linus' master at 509344b8b4d365b7ff3bce97198d83a57b7c3f31
> The tree is modified, but I doubt the patches I have can cause this. I attach
> then anyway. They never caused a conflict, so just the patches (in case of doubt
> I can push the tree somewhere).

I can confirm the same Oops on an unpatched kernel from Linus' git
(v2.6.36-rc4-134-g03a7ab0). I have a Logitech G500 mouse.

> The oops is reproducable. lsusb hangs (D state) after the oops.

However on my machine lsusb doesn't hang.

  reply	other threads:[~2010-09-18 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18  9:30 OOPS in hiddev_open on connecting "Logitech MX620 Laser Cordless Mouse" Alex Riesen
2010-09-18 13:36 ` Andreas Bombe [this message]
2010-09-18 17:56 ` Jiri Kosina
2010-09-18 19:41   ` Andreas Bombe
2010-09-18 20:59   ` Alex Riesen
  -- strict thread matches above, loose matches on Subject: below --
2010-09-18  9:48 Mat
2010-09-18 18:09 ` Jiri Kosina
2010-09-18 19:24   ` Mat
2010-09-18 19:36     ` Jiri Kosina

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=20100918133610.GA4554@amos.infernal \
    --to=aeb@debian.org \
    --cc=arnd@arndb.de \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /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