mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Moritz Muehlenhoff <jmm@informatik.uni-bremen.de>
To: linux-kernel@vger.kernel.org
Subject: Keyboard freezes on SIS630 based Clevo notebooks
Date: Thu, 29 Aug 2002 21:05:33 +0200	[thread overview]
Message-ID: <20020829190533.GA11223@informatik.uni-bremen.de> (raw)

Hi,
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. No keyboard
input at all is accepted while the machine itself continues to work
properly (processes continue to write to stdout and I can login and 
continue to work through SSH). The freezes occur approx. at least once
a week and sometimes three times a day, so there's no real pattern behind
it.

A friend of mine owns the same model and the same problems occur; I also
found a website stating the same problems on it; so it's of general nature
and not specific to my hardware. I didn't find any information about these
freezes running Windows, so I guess it's Linux-kernel specific and not a sole
hardware issue.

The system freezed on all kinds of kernel, either 2.4 and 2.5, either
vanilla and heavily patched.

So, the big question: Which data would I need to collect on the next freeze
that would allow an experienced kernel hacker to track down the problem?

This nasty bug is the only thing in the way to a perfect Linux notebook,
everything else works just perfect.

TIA,
         Moritz

             reply	other threads:[~2002-08-29 19:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 19:05 Moritz Muehlenhoff [this message]
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

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=20020829190533.GA11223@informatik.uni-bremen.de \
    --to=jmm@informatik.uni-bremen.de \
    --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®