From: Andrew Morton <akpm@osdl.org>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: Fw: Oops with 2.6.13-rc6-mm2 and USB mouse
Date: Sat, 27 Aug 2005 15:31:57 -0700 [thread overview]
Message-ID: <20050827153157.47ac39d2.akpm@osdl.org> (raw)
In-Reply-To: <20050827200904.GA4362@ime.usp.br>
Rogério Brito <rbrito@ime.usp.br> wrote:
>
> Hi, Andrew.
>
> I just tested the USB mouse with 2.6.13-rc6-mm2 and ACPI disabled
> (which, according to Linus, is one of the "usual suspects") and the
> problem still occurred.
>
> On the other hand, with kernel 2.6.13-rc5-mm1 (which I am running now),
> I didn't have any problems plugging and unplugging the mouse. Here are
> the messages I get in dmesg (2.6.13-rc5-mm1) after I plug/unplug the
> mouse:
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> usb 1-1.2: new low speed USB device using uhci_hcd and address 4
> input: USB HID v1.00 Mouse [USB Wheel Mouse] on usb-0000:00:04.2-1.2
> usb 1-1.2: USB disconnect, address 4
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> Just thought you might like to know about this. If you want me to test
> any other version, please let me know.
>
Unfortunately there are 71 USB patches in 2.6.13-rc6-mm2 and I don't know
which ones to suspect.
Hopefully Greg (when he returns) or one of the other USB developers can
identify the buggy patch - we wouldn't want this leaking into Linus's
kernel..
next prev parent reply other threads:[~2005-08-27 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050826220618.7365e690.akpm@osdl.org>
2005-08-27 20:09 ` Fw: Oops with 2.6.13-rc6-mm2 and USB mouse Rogério Brito
2005-08-27 20:39 ` Mattia Dongili
2005-08-28 21:53 ` Ed Tomlinson
2005-08-27 22:31 ` Andrew Morton [this message]
2005-08-28 12:55 ` Mattia Dongili
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=20050827153157.47ac39d2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rbrito@ime.usp.br \
/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