From: Pavel Machek <pavel@suse.cz>
To: Ivan Borissov Ganev <ganev@cc.gatech.edu>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.4.[01] lockups
Date: Sun, 11 Feb 2001 21:02:19 +0100 [thread overview]
Message-ID: <20010211210219.F3748@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.20.0102070207300.1226-500000@gamspc7.ihep.su> <Pine.SOL.4.21.0102061907230.7348-100000@tuomotu.cc.gatech.edu>
In-Reply-To: <Pine.SOL.4.21.0102061907230.7348-100000@tuomotu.cc.gatech.edu>; from Ivan Borissov Ganev on Tue, Feb 06, 2001 at 07:41:51PM -0500
Hi!
> I am experiencing a problem with both 2.4.0 and 2.4.1. The problem is that
> at seemingly random times the console locks up. After the lockup I can no
> longer type and the mouse is frozen. As far as I can tell, other systems
> services are not affected, i.e. programs continue to run, music is being
> played, I/O is fine. It looks like _only_ the console devices are locked
> up.
Login via network or serial cable, and see if /proc/interrupts entry
for keyboard/mouse changes as you type. Attempt to blink keyboard leds
with setleds.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-12 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 2:27 Problems with Linux 2.4.1 Alexander Zvyagin
2001-02-07 0:41 ` [BUG] 2.4.[01] lockups Ivan Borissov Ganev
2001-02-11 20:02 ` Pavel Machek [this message]
2001-02-12 13:23 ` Ville Herva
2001-02-15 5:31 ` Ivan Borissov Ganev
2001-02-07 3:22 ` Problems with Linux 2.4.1 Brad Douglas
2001-02-07 9:24 ` Alan Cox
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=20010211210219.F3748@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=ganev@cc.gatech.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
all inboxes | Powered by JetHome®