From owner-freebsd-mobile  Mon Jan  6 22:34:03 1997
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id WAA01813
          for mobile-outgoing; Mon, 6 Jan 1997 22:34:03 -0800 (PST)
Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id WAA01807
          for <mobile@freebsd.org>; Mon, 6 Jan 1997 22:33:47 -0800 (PST)
Received: by nasu.utsunomiya-u.ac.jp (5.57/ULTRIX-940302)
	id AA11554; Tue, 7 Jan 97 15:32:09 +0900
Received: by outmail.utsunomiya-u.ac.jp (5.57/ULTRIX-940909)
	id AA10388; Tue, 7 Jan 97 15:32:08 +0900
Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id PAA05864; Tue, 7 Jan 1997 15:35:35 +0900 (JST)
Message-Id: <199701070635.PAA05864@zodiac.mech.utsunomiya-u.ac.jp>
To: Brian Beattie <beattie@aracnet.com>
Cc: mobile@freebsd.org, Nate Williams <nate@mt.sri.com>,
        yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: Tecra 730 keyboard problem update 
In-Reply-To: Your message of "Mon, 06 Jan 1997 04:31:53 PST."
             <Pine.NEB.3.95.970106042211.1720B-100000@eris.beattie.aracnet.com> 
References: <Pine.NEB.3.95.970106042211.1720B-100000@eris.beattie.aracnet.com> 
Date: Tue, 07 Jan 1997 15:35:34 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Now that I have got the network card working to my statisfaction, I
>am running X.  I have seen two keyborad lockups so far.  One did not
>respond to any of the shift/control/alt keys so far as I can tell but
>it also did not clear on server reset.  The second one I did not try
>the shift/control/alt keys but it did clear on server reset.
>
>I did notice each time that there was a "click" of the disk drive
>almost as if there was a disk sync just as the keyboard locked up.  

I have little idea why the disk activity occurs like this.  Well,
syslogd may be logging something (to /var/log/messages by default).
Do you see any unusual log messages? However, the syscons/psm/kbdio
drivers in 2.2-BETA don't send log messages to syslogd after the
system boot by default. So, even if you find something, it does not
directly come from the drivers.

>I will keep trying to see if I can get any more information, if there
>is anything anybody can think of that I can try, to trap this problem
>let me know.  Other than the keyboard, it is working great.
>
>Thanks
>
> 
>Brian Beattie                   | From an MIT job ad "Applicants must also hav
>e 

Thank you for your report, and I am sorry that I cannot be of more
help to you at this time.

Kazu