linux-kernel - Re: keyboard dead with 45b5035

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>] [day] [month] [year] [list]

Message-ID: <47B9CCB5.7080703@lwfinger.net>
Date:	Mon, 18 Feb 2008 11:21:41 -0700
From:	Larry Finger <Larry.Finger@...inger.net>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: keyboard dead with 45b5035 - Regression in 2.6.25-rc2

 > The patch "[RTNETLINK]: Send a single notification on device state changes." kills (at least) the 
 > keyboard here. Everything seems to work fine in single user mode, but when init starts spawning 
of > logins, the keyboard goes bye-bye. Even the power button is ignored. :/
 >
 > I've tried just creating another vt with "chvt 2", but that is insufficient to trigger the bug.

I can confirm this problem. On my system it is not triggered by logins as my system boots into KDE, 
but as soon as NetworkManager starts and/or makes a connection, the problem is triggered. The 
wireless system is being used. I found the problem by bisection and confirmed that 
v2.6.25-rc2-238-gb45e229 will work OK if that commit is reverted.

Larry


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