[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0907281031020.2881-100000@iolanthe.rowland.org>
Date: Tue, 28 Jul 2009 10:33:46 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Valdis.Kletnieks@...edu
cc: Andrew Morton <akpm@...ux-foundation.org>,
David Brownell <dbrownell@...rs.sourceforge.net>,
Jiri Kosina <jkosina@...e.cz>,
Greg Kroah-Hartman <gregkh@...e.de>,
<linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>
Subject: Re: 31-rc3-mmotm0716 - dead USB trackball mouse kills entire system
On Mon, 27 Jul 2009 Valdis.Kletnieks@...edu wrote:
> Confirming - the patch in that thread prevents the system lockup I was
> seeing.
>
> So it looks like hid_reset() getting more chatty sometime in the last 2 weeks
> was a red herring, and one I can't actually complain about - it was quite
> legitimately whinging about not being able to reset a device that was in fact
> dead in the water at the time. Given that, and a working patch for ehci-hcd.c,
> I'm having a hard time finding the enthusiasm to track down what exactly
> changed in hid-core.c. :)
>
> The change in hid-core.c behavior just had the bad luck to land in -mmotm at
> the exact same time the bug in ehci-hcd.c landed. So we had two user-visible
> behavior changes in the same area of code at the same time. Hilarity ensues. :)
>
> Thanks for pointing me at the actual fix. ;)
A question for you: Do you now observe any warnings in the dmesg log if
you rmmod ehci-hcd after the trackball mouse is gone? Apparently the
patch you tested isn't perfect and some stuff gets leaked. I'm trying
to track down the problem.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists