linux-kernel - Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4af2d03a0703130913n3f51a3ffiec6e498c56a34826@mail.gmail.com>
Date:	Tue, 13 Mar 2007 17:13:08 +0100
From:	"Jiri Slaby" <jirislaby@...il.com>
To:	"Alan Stern" <stern@...land.harvard.edu>
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 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.

> 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?

I'm away from the box till Sat, anyway.

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
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/