mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.5.42+ reboot kills Dell Latitude keyboard
Date: Thu, 17 Oct 2002 13:18:05 +0200	[thread overview]
Message-ID: <15790.40045.655146.814922@kim.it.uu.se> (raw)
In-Reply-To: <m1zntd1kdg.fsf@frodo.biederman.org>

Eric W. Biederman writes:
 > Mikael Pettersson <mikpe@csd.uu.se> writes:
 > 
 > > Dell Latitude CPi laptop. Boot 2.5.42 or .43, then reboot.
 > > Shortly after the screen is blanked and the BIOS starts, it
 > > prints a "keyboard error" message and requests an F1 or F2
 > > response (continue or go into SETUP). Never happened with any
 > > other kernel on that machine.
 > > 
 > > Apparently the 2.5.42+ "let's shut everything down at reboot"
 > > change
 > 
 > There was no such change just a discussion of what the kernel
 > has been doing since 2.5.8 or so.
 > 
 > > put the keyboard controller in a state which is inconsistent
 > > with the BIOS' expections at a warm boot.
 > 
 > There is a bug in device_suspend.  device_shutdown, and device_suspend
 > where merged and the POWER_DOWN case now removes the drivers which
 > is a bug.  You may be getting hit with that.
 > 
 > Eric Blade has posed a patch fixing that.

I tried Eric Blade's patch
<http://marc.theaimsgroup.com/?l=linux-kernel&m=103477012517984&w=2>
but it didn't make any difference. Same keyboard error as before.

So either the patch doesn't change what actions are taken on reboot,
or the keyboard (std SERIO_I8042 + ATKBD PC stuff) driver was also
broken in the 2.5.41->2.5.42 step.

/Mikael

  reply	other threads:[~2002-10-17 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  8:41 Mikael Pettersson
2002-10-17  9:32 ` Eric W. Biederman
2002-10-17 11:18   ` Mikael Pettersson [this message]
2002-10-17 14:14     ` Eric W. Biederman
2002-10-16 14:39       ` dijital1

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=15790.40045.655146.814922@kim.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®