From: "Skip Tavakkolian" <fst@centurytel.net>
To: 9fans@cse.psu.edu
Subject: [9fans] cpu keyboard
Date: Thu, 5 Dec 2002 01:20:19 -0500 [thread overview]
Message-ID: <9295e66ae9f5e0ba2b19f08365ab8599@centurytel.net> (raw)
When using a 4th ed cpu kernel -- built locally -- the
console freezes within a few minutes of startup, although the system
continues to operate (drawterm and cpu ). The CD image was
downloaded on 11/27. The term kernel from the CD on the same hardware
doesn't exhibit this problem. Any idea where I should start looking?
Also, I can't be sure, but it seems to happen more quickly if I switch
the console (keyboard/mouse/display) to another machine and
back.
I vaguely recall seeing this with a 3rd ed cpu. Has anyone else
experienced this?
next reply other threads:[~2002-12-05 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 6:20 Skip Tavakkolian [this message]
2002-12-05 14:20 Skip Tavakkolian
2002-12-05 14:32 presotto
2002-12-05 14:48 Skip Tavakkolian
2002-12-05 17:19 Russ Cox
2002-12-05 17:42 Skip Tavakkolian
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=9295e66ae9f5e0ba2b19f08365ab8599@centurytel.net \
--to=fst@centurytel.net \
--cc=9fans@cse.psu.edu \
/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).