linux-kernel - Re: [git pull] Input updates for 2.6.34-rc6

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

Date:	Tue, 3 Aug 2010 23:29:54 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-input@...r.kernel.org, Bastien Nocera <hadess@...ess.net>,
	Anisse Astier <anisse@...ier.eu>
Subject: Re: [git pull] Input updates for 2.6.34-rc6

On Tue, Aug 03, 2010 at 11:20:22PM -0700, Dmitry Torokhov wrote:
> On Fri, May 14, 2010 at 08:16:34AM -0700, Linus Torvalds wrote:
> > 
> > 
> > On Fri, 14 May 2010, Matthew Garrett wrote:
> > >
> > > I've done some experimentation under qemu. On ACPI systems, Windows will 
> > > *only* touch the keyboard controller if there's a device with an 
> > > appropriate PNP HID or CID and if _STA evaluates to 0x0b or 0x0f. 
> > > Otherwise it'll simply ignore the hardware entirely. By the looks of it 
> > > their keyboard probing is also somewhat different to ours, but that's 
> > > probably another story.
> > 
> > Well, I'd hate to lose the keyboard hotplug capability, but at the same 
> > time, it _is_ 2010, and while I have personally used it historically, I 
> > don't really foresee ever using it again.
> > 
> > So we _could_ decide to just try it, and see if anybody screams. If nobody 
> > does, that would be a very simple solution to the problem.
> > 
> 
> OK, time to ressurect the topic ;)
> 
> There is another report (from Anisse - CCed) - MSI AE2220 stops for 10
> seconds when we try to see if "AUX DISABLE" command took effect (it
> doesn't). While we should reduce the time we wait and retry to something
> more reasonable it woudl not fix this issue completely.
> 

Hm, I take it back.. We won't be able to reduce timeout because we don't
hit that code yet. Here is the excerpt from dmesg:

[    0.500931] drivers/input/serio/i8042.c: a7 -> i8042 (command) [9]
[    0.502950] drivers/input/serio/i8042.c: 20 -> i8042 (command) [10]
[    0.502950] drivers/input/serio/i8042.c:      -- i8042 (timeout) [10]
[   11.045100] Failed to disable AUX port, but continuing anyway... Is this a SiS?
[   11.049741] If AUX port is really absent please use the 'i8042.noaux' option.
[   11.055417] drivers/input/serio/i8042.c: a8 -> i8042 (command) [13]
[   11.057436] drivers/input/serio/i8042.c: 20 -> i8042 (command) [14]
[   11.057436] drivers/input/serio/i8042.c:      -- i8042 (timeout) [14]

We try do disable AUX and then read back the control register. We see
there isn't any data coming and then box goes away for 10 seconds.
And if we don't touch AUX port all is good...

> The box does not have any PS/2 ports but in this case BIOS writers _did_
> some crack and put PS/2 devices in DSDT. While the devices are most
> likely not active and thus Matthew's patch would help Anisse I do hate
> to loose the option of plugging PS/2 mouse/keyboard after boot and
> having chance of them working. I would still like to add a few blacklist
> entries instead.
> 

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