From owner-freebsd-current  Tue May 21 12:00:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA18564
          for current-outgoing; Tue, 21 May 1996 12:00:36 -0700 (PDT)
Received: from DeepCore.dk (aalb3.pip.dknet.dk [194.192.0.163])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA18558;
          Tue, 21 May 1996 12:00:30 -0700 (PDT)
Received: (from sos@localhost) by DeepCore.dk (8.7.5/8.7.3) id VAA01203; Tue, 21 May 1996 21:00:25 +0200 (MET DST)
Message-Id: <199605211900.VAA01203@DeepCore.dk>
Subject: Re: bad keyboard reset routine?
To: pst@shockwave.com (Paul Traina)
Date: Tue, 21 May 1996 21:00:24 +0200 (MET DST)
Cc: sos@FreeBSD.org, current@FreeBSD.org
In-Reply-To: <199605211824.LAA00264@precipice.shockwave.com> from Paul Traina at "May 21, 96 11:24:57 am"
From: sos@FreeBSD.org
Reply-to: sos@FreeBSD.org
X-Mailer: ELM [version 2.4ME+ PL15 (25)]
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 Paul Traina who wrote:
> In a -current system as of this morning, I'm now getting:
> 
> scprobe: keyboard RESET failed (result = 0xfa)
> sc0 at 0x60-0x6f irq 1 on motherboard
> sc0: VGA color <16 virtual consoles, flags=0x0>
> 
> I never received this before.

Me neither :)

> Is this something you should be aware of?

Maybe, I'm not up to current (just back from 8 holidays), and the
current reports of vm problems makes me a little hesitant to
upgrade just yet...


(back to mail reading...)

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