From: Andreas Bombe <aeb-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Alex Riesen <raa.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jiri Kosina <jkosina-AlSwsSmVLrQ@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-18 13:36 UTC|newest]
Thread overview: 7+ 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
[not found] ` <AANLkTikOowB=8=3cnJ0QgJNfBsVeMUrkNT0E0uH2LDXL-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-18 13:36 ` Andreas Bombe [this message]
2010-09-18 17:56 ` Jiri Kosina
2010-09-18 19:41 ` Andreas Bombe
[not found] ` <alpine.LNX.2.00.1009181954010.26813-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2010-09-18 20:59 ` Alex Riesen
[not found] <AANLkTimpXSrbZ6pAi3OWTmHrUnHPxwAnE1kEvmCj7G+r@mail.gmail.com>
[not found] ` <alpine.LNX.2.00.1009182008220.26813@pobox.suse.cz>
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-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=jkosina-AlSwsSmVLrQ@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=raa.lkml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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).