[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0703131225390.2509-100000@iolanthe.rowland.org>
Date: Tue, 13 Mar 2007 12:30:24 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Jiri Slaby <jirislaby@...il.com>
cc: Jiri Kosina <jikos@...os.cz>, <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]
On Tue, 13 Mar 2007, Jiri Slaby wrote:
> On 3/13/07, Alan Stern <stern@...land.harvard.edu> wrote:
> > I don't see anything in the UHCI snapshots to explain the difference in
> > behavior. One thing that stands out is the other, low-speed device (a
> > mouse?) -- in the bad kernel dump its driver was running and in the good
> > kernel dump its driver wasn't.
>
> There weren't any changes neither in HW config nor in modules, just
> reverted, compiled, installed, rebooted. Mouse is HID user too, so I
> don't know what was wrong with that.
Odd...
> > Can you get another pair of usbmon logs, starting from before you plug in
> > the keyboard? Don't bother with the UHCI snapshots for now.
>
> So, do you mean rmmod uhci_hcd, unplug the keyboard, modprobe
> uhci_hcd, start usbmon, plug the keyboard, press numlock, stop usbmon,
> post it?
Yes. In fact, let's be safe and unplug _both_ the mouse and the keyboard.
Then after starting usbmon, plug in only the keyboard.
> I'm away from the box till Sat, anyway.
Okay, no rush.
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