From: "Skip Tavakkolian" <skip.tavakkolian@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] keyboard/mouse get lost on dual cpu system
Date: Thu, 6 Dec 2007 15:57:37 -0800 [thread overview]
Message-ID: <84d462a30712061557n7151935ev25d4c10f6a6dedcf@mail.gmail.com> (raw)
In-Reply-To: <1fdb9cccd17f8276c0d13fb52c26d24a@quanstro.net>
it seems related to something geoff mentioned. i think if there's mouse activity
before rio start it causes it more. the only input that seems to work
is halt via ctl-alt-del.
i'll try to repro with more detail as soon as my emergency is over.
On Dec 6, 2007 3:44 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> > i'm building a new system using an image from April. i noticed that
> > on a dual proc machine keyboard or the mouse gets lost at some
> > point after rio starts. it never happens with only one cpu. anybody
> > else seeing this?
>
> are these ps/2 or usb devices?
> does killing rio solve the problem?
> does ^t^t or ^p work?
>
> - erik
>
next prev parent reply other threads:[~2007-12-06 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 23:40 Skip Tavakkolian
2007-12-06 23:44 ` erik quanstrom
2007-12-06 23:57 ` Skip Tavakkolian [this message]
2007-12-07 4:27 ` Bruce Ellis
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=84d462a30712061557n7151935ev25d4c10f6a6dedcf@mail.gmail.com \
--to=skip.tavakkolian@gmail.com \
--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).