mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Moritz Muehlenhoff <jmm@Informatik.Uni-Bremen.DE>
Cc: Padraig Brady <padraig.brady@corvil.com>, linux-kernel@vger.kernel.org
Subject: Re: Keyboard freezes on SIS630 based Clevo notebooks
Date: Fri, 30 Aug 2002 13:51:24 +0200	[thread overview]
Message-ID: <15727.23612.577930.303318@kim.it.uu.se> (raw)
In-Reply-To: <200208300926.g7U9Qa305884@x06.informatik.uni-bremen.de>

Moritz Muehlenhoff writes:
 > In stuga.ml.linux.kernel, you wrote:
 > >> I own a SIS630 based notebook from Baycom (model name "Worldbook II"), which
 > >> indeed is a rebrand from a Clevo/Kapok model (normal model name 2700C).
 > >> 
 > >> I'm experiencing occasional, unreproducable keyboard lockups.
 > > 
 > > Me too (2700).
 > > 
 > > If noticed the lockups occur when the "battery low"
 > > light starts flashing. I.E. it's realted to some
 > > APM event. Also the mouse is unresponsive for me
 > > when this happens.
 > 
 > There were some lockups when I connected the AC plug, but these
 > were rare and totally irreproducable as well.
 > Alan had the same idea as you and gave me the hint to rebuild
 > the kernel without APM and APIC.

Some laptops, including the Dell Inspiron ones, (a) don't tell the
kernel APM when they're about to do APM stuff, and (b) have a buggy
APM and/or SMM implementation that breaks if the kernel has enabled
the local APIC. The workaround is to not enable the local APIC. If
this fixes your machine, please post your machine's DMI strings so
we can update the local APIC blacklist rule set in dmi_scan.

Events that would break the Dells include pulling or inserting the
AC plug, and hitting the magic key combo to enter the BIOS screens.

/Mikael

      reply	other threads:[~2002-08-30 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 19:05 Moritz Muehlenhoff
2002-08-29 21:08 ` Vojtech Pavlik
2002-08-30  9:02 ` Padraig Brady
2002-08-30  9:26   ` Moritz Muehlenhoff
2002-08-30 11:51     ` Mikael Pettersson [this message]

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=15727.23612.577930.303318@kim.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=jmm@Informatik.Uni-Bremen.DE \
    --cc=linux-kernel@vger.kernel.org \
    --cc=padraig.brady@corvil.com \
    /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®