From finrod@ppp008.uio.no  Tue Feb 10 04:19:37 1998
Received: from ppp008.uio.no (ppp008.uio.no [129.240.240.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA15084
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 10 Feb 1998 04:19:30 -0800 (PST)
          (envelope-from finrod@ppp008.uio.no)
Received: (from root@localhost)
	by ppp008.uio.no (8.8.8/8.8.8) id MAA00949;
	Tue, 10 Feb 1998 12:19:54 GMT
	(envelope-from finrod)
Message-Id: <199802101219.MAA00949@ppp008.uio.no>
Date: Tue, 10 Feb 1998 12:19:54 GMT
From: Dag-Erling Smrgrav <dag-erli@ifi.uio.no>
Reply-To: dag-erli@ifi.uio.no
To: FreeBSD-gnats-submit@freebsd.org
Subject: LPIP causes spurious reboots
X-Send-Pr-Version: 3.2

>Number:         5698
>Category:       i386
>Synopsis:       LPIP causes spurious reboots
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    des
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 10 04:20:01 PST 1998
>Closed-Date:    Tue Jan 11 07:20:59 PST 2000
>Last-Modified:  Tue Jan 11 07:21:33 PST 2000
>Originator:     Dag-Erling Coidan Smrgrav
>Release:        FreeBSD 2.2.5-STABLE i386
>Organization:
University of Oslo, Department of Informatics
>Environment:

finrod@ppp008 ~$ uname -a
FreeBSD ppp008.uio.no 2.2.5-STABLE FreeBSD 2.2.5-STABLE #0: Tue Feb 10 11:28:23 CET 1998     root@valinor.ewox.org:/usr/src/sys/compile/valinor  i386
finrod@ppp008 ~$ ident /sys/i386/isa/lpt.c
/sys/i386/isa/lpt.c:
     $Id: lpt.c,v 1.55.2.1 1996/11/12 09:08:38 phk Exp $
finrod@ppp008 ~$ ifconfig -au
lp0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.1.1 --> 10.0.1.2 netmask 0xff000000 
ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.0.1 netmask 0xff000000 broadcast 10.255.255.255
        ether 00:60:8c:61:df:38 
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
        inet 129.240.240.9 --> 129.240.240.1 netmask 0xffff0000 
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000 

This computer has an ASUSTek P/I XP55T2P4 rev. 1.3 motherboard with a
150 MHz Pentium Classic running at 166 MHz, 512 kB PB cache and 128 MB
EDO RAM.

Identical symptoms on a brand new IBM ThinkPad 380E (150 MHz Pentium
MMX, 16 MB RAM) with identical source tree.

Here's the kernel configuration for the 166 MHz:

#
# VALINOR - Classic Pentium 150 with Adaptec 2940UW
#


# Machine type and ident
machine		"i386"
cpu		"I586_CPU"
ident		valinor
maxusers	32


# General options
options		BOUNCE_BUFFERS
options		"AUTO_EOI_1"
#options	"AUTO_EOI_2"
options		"COMPAT_43"
options		INET


# File system
options		FFS
options		DEVFS
options		PROCFS


# XFree86 support
options		SYSVSHM
options		SYSVSEM
options		SYSVMSG
options		XSERVER


# Miscellaneous options
options		UCONSOLE
options		USERCONFIG
options		VISUAL_USERCONFIG


# Kernel name and location
config		kernel	root on sd0


# ISA and PCI bus
controller	isa0
controller	pci0
controller	pnp0


# Floppy controller with one drive
controller	fdc0	at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk		fd0	at fdc0 drive 0


# EIDE controller with one disk
controller	wdc0	at isa? port "IO_WD1" bio irq 14 vector wdintr
disk		wd0	at wdc0 drive 0


# Adaptec 2940UW controller with support for various devices
options		SCSI_DELAY=1
controller	ahc0
controller	scbus0
device		sd0
device		od0
device		st0
device		cd0


# System console
device		sc0	at isa? port "IO_KBD" tty irq 1 vector scintr
options		MAXCONS=8
options		SC_HISTORY_SIZE=400
#options	SC_SPLASH_SCREEN


# Numeric coprocessor
device		npx0	at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr


# Serial and parallel interfaces
device		sio0	at isa? port "IO_COM1" tty irq 4 vector siointr
device		sio1	at isa? port "IO_COM2" tty irq 3 vector siointr
device		lpt0	at isa? port? tty irq 7 vector lptintr


# 3Com Etherlink III
device ep0 at isa? port 0x300 net irq 10 vector epintr


# Networking pseudo-devices
pseudo-device	loop
pseudo-device	ether
pseudo-device	sl
pseudo-device	tun
pseudo-device	bpfilter


# Other pseudo-devices
pseudo-device	log
pseudo-device	vn
pseudo-device	pty	64
pseudo-device	gzip


>Description:

Running IP over LP causes spurious hangs and reboots, usually after
transferring barely a couple of megabytes. netstat(1) shows a
sustained raw transfer rate of 90 kBps for 30-60 seconds; then one of
the computers seems to run into a brick wall, and either freezes solid
or spontaneously reboots.

The 2.2.2R GENERIC kernel (from the 2.2.2 boot floppy) on the exact
same computers exhibits no such symptoms. With 2.2.2 talking to 2.2.2
over a laplink cable, I've been able to transfer the entire (tarred)
2.2.5-STABLE source tree, most of the FreeBSD 2.2.2R distribution
archives (from the CD-ROM) and the complete XFree86 3.3.1 (binaries
*and* source) distribution - a total of half a gigabyte or something.
With 2.2.5 talking to 2.2.5 or 2.2.5 talking to 2.2.2, nothing goes.

I haven't tried a 2.2.5 GENERIC kernel.

>How-To-Repeat:

% ifconfig lp0 10.0.1.1 10.0.1.2

Then exchange large quantities of data over lp0.

>Fix:
	
I wish I knew...

>Release-Note:
>Audit-Trail:

From: Duncan Barclay <dmlb@ragnet.demon.co.uk>
To: freebsd-gnats-submit@freebsd.org, dag-erli@ifi.uio.no
Cc:  Subject: Re: i386/5698: LPIP causes spurious reboots
Date: Tue, 24 Mar 1998 20:49:38 -0000 (GMT)

 Summary of my experiences using PLIP on FreeBSD 2.2.5, with
 one 5x86-133 with 20MB RAM and a 486/25 with 4MB Contura laptop.
 
   - sometimes when using a fast and slow machine (eg.P100 and 486/25)
     the fast machine crashes when you do big transfers. I think it
     is due to buffer overruns on the slow machine side and the fast
     machine doesnt deal with this well. The work around is to get the
     slow machine to be the initiator end of any xfer, i.e. slow machine
     is saying "give me next block" or "here's the next block". Be warned
     things like ftp and rcp have different initiator ends.
   - NFS works (bearing in mind the above, use the old reduce the
     block size hack, although I never tried it). However, due to
     the way an RPC is implemented in FreeBSD, portmap/mountd attaches
     itself to the first network interface (for things like getting
     a hostname etc.) which is often lp0 (depends on kernel config). This
     is a pain because the RPC code can't handle a point to point
     interface (like PLPI or PPP) and you don't get a running mountd.
     Workaround is to add a static route use
 
     # to enable rpc to work with a PLIP network (rpc binds to the first
     # network interface it finds an lp0 is found v. early)
     static_routes="loop_lp0"
     route_loop_lp0="192.168.201.32 127.0.0.1 1"
 
 ---
 ________________________________________________________________________
 Duncan Barclay          | God smiles upon the little children,
 dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned.
 ________________________________________________________________________

From: Peter Jeremy <peter.jeremy@auss2.alcatel.com.au>
To: freebsd-gnats-submit@FreeBSD.ORG
Cc:  Subject: Re: i386/5698: LPIP causes spurious reboots
Date: Tue, 24 Nov 1998 08:28:32 +1100

 See also kern/6099
 
 Peter
Responsible-Changed-From-To: freebsd-bugs->des 
Responsible-Changed-By: des 
Responsible-Changed-When: Sun Feb 7 17:51:41 PST 1999 
Responsible-Changed-Why:  
I'm working on PLIP. 
State-Changed-From-To: open->closed 
State-Changed-By: des 
State-Changed-When: Tue Jan 11 07:20:59 PST 2000 
State-Changed-Why:  
The newbus version of LPIP fixes these problems for -CURRENT. No attempt will 
be made to fix them in -STABLE. 
>Unformatted:
