linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: linux-kernel@vger.kernel.org
Subject: 2.5.14-rc1-mm1.5 - keyboard wierdness
Date: Wed, 21 Sep 2005 23:35:16 -0400	[thread overview]
Message-ID: <200509220335.j8M3ZGEJ004230@turing-police.cc.vt.edu> (raw)

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

I've had this happen twice now, running Andrew's "not quite -mm2" patch.

Symptoms: After about 20-30 minutes uptime, a running gkrellm shows system mode
suddenly shoot up to 99-100%, and the keyboard dies.  Oddly enough, a USB mouse
continued working, and the X server was still quite responsive (I was able to
close Firefox by opening a menu with the mouse and selecting 'quit', for
example).

alt-sysrq-foo still worked, but ctl-alt-N to switch virtual consoles didn't.
sysrq-t produced a trace with nothing obviously odd - klogd, syslog, and the
disk were all working.

Nothing interesting in the syslog - no oops, bug, etc..

Another odd data point (I didn't notice if this part happened the first time):
gkrellm reported that link ppp0 had inbound packets on the modem port of a
Xircom ethernet/modem combo card.  At the rate of 3.5M/second - a neat trick
for a 56K modem.  When I unplugged the RJ-11, gkrellm *kept* reporting the
inbound traffic.  When I ejected the card, *then* the ppp0 (and the alleged
inbound packets) stopped - but still sitting at 99% system and no keyboard.

This ring any bells?  Any suggestions for instrumentation to help debug this?

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

             reply	other threads:[~2005-09-22  3:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22  3:35 Valdis.Kletnieks [this message]
2005-09-22  4:00 ` 2.5.14-rc1-mm1.5 - keyboard wierdness Dmitry Torokhov
2005-09-22  4:19   ` Valdis.Kletnieks

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=200509220335.j8M3ZGEJ004230@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --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;
as well as URLs for NNTP newsgroup(s).