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 for Android: free password hash cracker in your pocket

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

Message-ID: <45FD5EA1.6040706@gmail.com>
Date:	Sun, 18 Mar 2007 16:45:37 +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]

Alan Stern napsal(a):
> On Sun, 18 Mar 2007, Jiri Slaby wrote:
> 
>> Alan Stern napsal(a):
>>> In drivers/usb/host/uhci-q.c, near the start is a function named
>>> uhci_fsbr_on().  Put a "return" statement right at its beginning so that
>>> the function doesn't do anything.  Does that make any difference?
>> Yes, it works.
> 
> Okay.  Take out that extra "return" statement and revert the WARN_ON, and
> try this patch.  I don't like it because it adds extra PCI bus overhead to
> the driver, but if some systems need it then there's no choice.

Yes, I'm proud to let you know, that it solves the problem :).

thanks a lot,
-- 
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

Hnus <hnus@...muni.cz> is an alias for /dev/null
-
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/