public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Stefan Seyfried <seife@suse.de>
Cc: nigel@suspend2.net, Pavel Machek <pavel@ucw.cz>,
	LKML <linux-kernel@vger.kernel.org>,
	dmitry.torokhov@gmail.com
Subject: Re: Failure to properly reinit i8042 post suspend-to-ram
Date: Tue, 10 Jul 2007 10:59:57 +1000	[thread overview]
Message-ID: <200707101059.57881.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <20070706150451.GA11400@suse.de>

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

Hi.

On Saturday 07 July 2007 01:04:51 Stefan Seyfried wrote:
> On Thu, Jul 05, 2007 at 09:04:27PM +1000, Nigel Cunningham wrote:
> > > 
> > > If confusion persist after 4 seconds hard power down... then you h ve
> > > hw/BIOS problem. Complain to whoever is manufacturing that beast.
> > 
> > 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 :)

Nigel
-- 
Nigel Cunningham
Christian Reformed Church of Cobden
103 Curdie Street, Cobden 3266, Victoria, Australia
Ph. +61 3 5595 1185 / +61 417 100 574
Communal Worship: 11 am Sunday.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-07-10  0:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22  6:07 Failure to properly reinit i8042 post suspend-to-ram Nigel Cunningham
2007-06-24 21:03 ` Rafael J. Wysocki
2007-06-24 23:18   ` Nigel Cunningham
2007-07-05 10:15 ` Pavel Machek
2007-07-05 11:04   ` Nigel Cunningham
2007-07-06 15:04     ` Stefan Seyfried
2007-07-06 23:01       ` Nigel Cunningham
2007-07-10  0:59       ` Nigel Cunningham [this message]
2007-07-10 12:04         ` Stefan Seyfried

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200707101059.57881.nigel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=seife@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox