From owner-freebsd-current  Thu Dec  3 22:36:58 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA26543
          for freebsd-current-outgoing; Thu, 3 Dec 1998 22:36:58 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26535
          for <current@FreeBSD.ORG>; Thu, 3 Dec 1998 22:36:55 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA06444;
	Fri, 4 Dec 1998 17:36:36 +1100
Date: Fri, 4 Dec 1998 17:36:36 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199812040636.RAA06444@godzilla.zeta.org.au>
To: hasty@rah.star-gate.com, seggers@semyam.dinoco.de
Subject: Re: nlpt and severe system slow down
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> controller      ppbus0
>> controller      ppc0    at isa?  irq 7 vector ppcintr
>> device          nlpt0   at ppbus?       
>
>Mine is this:
>
>controller      ppbus0
>device          nlpt0   at ppbus?
>device          plip0   at ppbus?
>controller      ppc0    at isa? port ? tty irq 7 vector ppcintr
>controller      ppc1    at isa? port ? tty irq 5 vector ppcintr
>
>I added the plip0 entry to be able to attach another system to plip1
>one day.  None connected, yet and plip1 is not configured by the
>network code during startup.

The device class should be "net" for plip.  See the plip man page.
This is incompatible (*) with the device class being tty or cam - you
should only use ppc for one of nlpt, plip or vpo.

(*) Except when slip is statically configured, net and tty are essentially
the same for statically configured devices.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message