From owner-freebsd-current  Wed Nov 13 10:17:07 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA03546
          for current-outgoing; Wed, 13 Nov 1996 10:17:07 -0800 (PST)
Received: from ravenock.cybercity.dk (disn48.cybercity.dk [194.16.57.48])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA03541;
          Wed, 13 Nov 1996 10:17:00 -0800 (PST)
Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id TAA16764; Wed, 13 Nov 1996 19:18:13 +0100 (MET)
Message-Id: <199611131818.TAA16764@ravenock.cybercity.dk>
Subject: Re: your mail
To: nate@mt.sri.com (Nate Williams)
Date: Wed, 13 Nov 1996 19:18:00 +0100 (MET)
From: "Soren Schmidt" <sos@ravenock.cybercity.dk>
Cc: sos@FreeBSD.org, nate@mt.sri.com, jkh@time.cdrom.com,
        wangel@wgrobez1.remote.louisville.edu, freebsd-current@FreeBSD.org
In-Reply-To: <199611131730.KAA00439@rocky.mt.sri.com> from "Nate Williams" at Nov 13, 96 10:30:43 am
From: sos@FreeBSD.org
Reply-to: sos@FreeBSD.org
X-Mailer: ELM [version 2.4 PL25 ME8b]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

In reply to Nate Williams who wrote:
> 
> 
> > > > > Has anyone been looking into why the Keyboard spastically locks up?  We
> > > > > know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel
> > > > > /dev/mem)by telnetting into the 'locked' machine by another machine.  Not
> > > > > a problem, and it works, but what if people don't have another machine?
> > > > 
> > > > That's been fixed in -current with Soren's latest syscons changes.
> > > 
> > > The fix also broke PS/2 mouse support. :( :(
> > 
> > I know :(, but so long as we occasionally looses an interrupt, there
> > is not much else to do. Or merge syscons and the ps/2 mousedriver.
> > (which I have on my TODO list)
> 
> Are we losing interrupts, or is there something else going on?

Yes we are loosing interrupts, mostly on very fast machines :(
I don't know how & why, but I guess its a symptom for the same
failure that made me put in the timeout code in wd.c years
ago :( :(

> Also, I just spoke with someone (the recent psm.c author) who is willing
> to do the work to integrate the two, so hopefully you two can resolve
> this.

Great!, I have a pretty good idea on how the it should be done...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
                Even more code to hack -- will it ever end
..