linux-kernel - Re: Failure to properly reinit i8042 post suspend-to-ram

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, 10 Jul 2007 14:04:08 +0200
From:	Stefan Seyfried <seife@...e.de>
To:	Nigel Cunningham <nigel@...el.suspend2.net>
Cc:	nigel@...pend2.net, Pavel Machek <pavel@....cz>,
	LKML <linux-kernel@...r.kernel.org>, dmitry.torokhov@...il.com
Subject: Re: Failure to properly reinit i8042 post suspend-to-ram

Hi,

On Tue, Jul 10, 2007 at 10:59:57AM +1000, Nigel Cunningham wrote:
> On Saturday 07 July 2007 01:04:51 Stefan Seyfried wrote:
> > On Thu, Jul 05, 2007 at 09:04:27PM +1000, Nigel Cunningham wrote:
> > > 
> > > Adding i8042.reset=1 to the commandline fixed it.
> > 
> > Wasn't there a quirk list where workarounds for i8042 on known bad machines
> > are stored? Maybe it would be a good idea to get your machine into it ;-)
> 
> Unless I'm missing something, it looks like there's no such thing in the i8042 
> driver. That's okay. I can cope with adding i8042.reset=1 to my 
> commandline :)

In drivers/input/serio/i8042-x86ia64io.h there are tables for various quirks,
but apparently nothing for "reset=1".
If we find another machine that needs reset=1, then it might be time for a
table for this quirk.

Best regards,

    Stefan

-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
-
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/