From owner-freebsd-current  Tue Dec 12 00:58:02 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA21674
          for current-outgoing; Tue, 12 Dec 1995 00:58:02 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA21667
          Tue, 12 Dec 1995 00:57:54 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA23824; Tue, 12 Dec 1995 19:55:39 +1100
Date: Tue, 12 Dec 1995 19:55:39 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199512120855.TAA23824@godzilla.zeta.org.au>
To: current@freebsd.org, sos@freebsd.org, uhclem%nemesis@fw.ast.com
Subject: Re: WHAT is going on in -current ???????
Cc: jkh@freebsd.org
Sender: owner-current@freebsd.org
Precedence: bulk

>[0]On top of that the matcd driver no longer works, it read a couble
>[0]of block then hangs on "netio" :(
>[0]
>[0]Oh boy I thought I was getting back into business again, and
>[0]then this mess.....

>Uh, the changes made since 2.1.0-RELEASE to matcd in -current were NOT made
>by the author of the matcd driver.  Other feet have trod on this rug.

"netio" has nothing to do with matcd anyway.  It is for sockets.

>Try going back to the driver from 2.1.0-RELEASE.  If it doesn't work,
>then some underlying kernel service has been broken or is in a
>transient state.

There's no chance that it would work.  Drivers are now required to
initialize their devswitch entries directly.

Bruce