From owner-freebsd-stable Mon Aug 5 07:05:17 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19431 for stable-outgoing; Mon, 5 Aug 1996 07:05:17 -0700 (PDT) Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA19400; Mon, 5 Aug 1996 07:05:05 -0700 (PDT) Received: from sierra.zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.7.3) with ESMTP id JAA16614; Mon, 5 Aug 1996 09:05:02 -0500 (CDT) Message-Id: <199608051405.JAA16614@sierra.zyzzyva.com> To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: ep0 problems and the stable tree In-reply-to: randy's message of Sat, 03 Aug 1996 16:38:33 -0500. <199608032138.QAA11489@sierra.zyzzyva.com> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Aug 1996 09:05:02 -0500 From: Randy Terbush Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm would like to add the following to my previous post and bring this on to the current list, since the -stable list appears to be deserted... I can further pin this behavior down to TCP NFS connections. UDP does not seem to be aflicted, but it is easily recreated over a TCP NFS connection. Is there any chance that the "grinding to a halt" reports on -current are network related? > I've seen a lot of discussion about the ep driver getting broken late > in the 2.1.5 release. Should I still be seeing this from sources dated > > sierra:/sys/i386/isa > #> ll if_ep* > -rw-r--r-- 1 root wheel 36464 Jul 15 23:10 if_ep.c > -rw-r--r-- 1 root wheel 36457 May 26 14:54 if_ep.c.orig > -rw-r--r-- 1 root wheel 13946 Mar 31 23:08 if_epreg.h > > Aug 3 16:11:25 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > Aug 3 16:13:49 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > Aug 3 16:13:52 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > > > The net result is that a new NFS client on the net is suddenly freezing > quite frequently. Killing and restarting the 'nfsd' processes on the > server fix the problem. > > Secondly, do I dare sup the -stable tree at this point? What was decided? > > > > From owner-freebsd-stable Mon Aug 5 10:48:51 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA06033 for stable-outgoing; Mon, 5 Aug 1996 10:48:51 -0700 (PDT) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA06028 for ; Mon, 5 Aug 1996 10:48:48 -0700 (PDT) Received: by havenx.uniserve.com id <18264-22441>; Mon, 5 Aug 1996 10:52:21 -0800 Date: Mon, 5 Aug 1996 10:52:18 -0700 (PDT) From: Tom Samplonius To: Randy Terbush cc: freebsd-stable@freebsd.org Subject: Re: ep0 problems and the stable tree In-Reply-To: <199608051405.JAA16614@sierra.zyzzyva.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 5 Aug 1996, Randy Terbush wrote: > I'm would like to add the following to my previous post and > bring this on to the current list, since the -stable list appears > to be deserted... > > I can further pin this behavior down to TCP NFS connections. > UDP does not seem to be aflicted, but it is easily recreated > over a TCP NFS connection. > > Is there any chance that the "grinding to a halt" reports on > -current are network related? > > > I've seen a lot of discussion about the ep driver getting broken late > > in the 2.1.5 release. Should I still be seeing this from sources dated > > > > sierra:/sys/i386/isa > > #> ll if_ep* > > -rw-r--r-- 1 root wheel 36464 Jul 15 23:10 if_ep.c > > -rw-r--r-- 1 root wheel 36457 May 26 14:54 if_ep.c.orig > > -rw-r--r-- 1 root wheel 13946 Mar 31 23:08 if_epreg.h > > > > Aug 3 16:11:25 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > > Aug 3 16:13:49 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > > Aug 3 16:13:52 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > > > > > > The net result is that a new NFS client on the net is suddenly freezing > > quite frequently. Killing and restarting the 'nfsd' processes on the > > server fix the problem. What kind of 3COM card are you using? Some 3COM cards have very limited buffer space (8k ?), and will get buffer overflow very easily if your computer can't keep service interupts fast enough. This would explain why TCP would be effect, becasue TCP would transfer a whole window of packets at once, which would flood your buffer space. BTW, I ignored your first message to -stable because your never said what kind of card you were using, because if you are using one of the good cards, I'd wasting your and my time. Tom From owner-freebsd-stable Mon Aug 5 15:02:21 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA25207 for stable-outgoing; Mon, 5 Aug 1996 15:02:21 -0700 (PDT) Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA25198 for ; Mon, 5 Aug 1996 15:02:17 -0700 (PDT) Received: from sierra.zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.7.3) with ESMTP id RAA27788; Mon, 5 Aug 1996 17:02:07 -0500 (CDT) Message-Id: <199608052202.RAA27788@sierra.zyzzyva.com> To: Tom Samplonius cc: Randy Terbush , freebsd-stable@freebsd.org Subject: Re: ep0 problems and the stable tree In-reply-to: tom's message of Mon, 05 Aug 1996 10:52:18 -0700. X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Aug 1996 17:02:06 -0500 From: Randy Terbush Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 3c509 combo Would it not evenutally catch up? > > On Mon, 5 Aug 1996, Randy Terbush wrote: > > > I'm would like to add the following to my previous post and > > bring this on to the current list, since the -stable list appears > > to be deserted... > > > > I can further pin this behavior down to TCP NFS connections. > > UDP does not seem to be aflicted, but it is easily recreated > > over a TCP NFS connection. > > > > Is there any chance that the "grinding to a halt" reports on > > -current are network related? > > > > > I've seen a lot of discussion about the ep driver getting broken late > > > in the 2.1.5 release. Should I still be seeing this from sources dated > > > > > > sierra:/sys/i386/isa > > > #> ll if_ep* > > > -rw-r--r-- 1 root wheel 36464 Jul 15 23:10 if_ep.c > > > -rw-r--r-- 1 root wheel 36457 May 26 14:54 if_ep.c.orig > > > -rw-r--r-- 1 root wheel 13946 Mar 31 23:08 if_epreg.h > > > > > > Aug 3 16:11:25 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > > > Aug 3 16:13:49 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > > > Aug 3 16:13:52 sierra /kernel: ep0: Status: 2002 (input buffer overflow) > > > > > > > > > The net result is that a new NFS client on the net is suddenly freezing > > > quite frequently. Killing and restarting the 'nfsd' processes on the > > > server fix the problem. > > What kind of 3COM card are you using? Some 3COM cards have very > limited buffer space (8k ?), and will get buffer overflow very easily if > your computer can't keep service interupts fast enough. > > This would explain why TCP would be effect, becasue TCP would transfer > a whole window of packets at once, which would flood your buffer space. > > BTW, I ignored your first message to -stable because your never said > what kind of card you were using, because if you are using one of the > good cards, I'd wasting your and my time. > > Tom From owner-freebsd-stable Thu Aug 8 09:32:17 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA19029 for stable-outgoing; Thu, 8 Aug 1996 09:32:17 -0700 (PDT) Received: from prometeo.prometeo.it (prometeo.prometeo.it [194.21.36.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA18999; Thu, 8 Aug 1996 09:32:10 -0700 (PDT) Received: from gioc.prometeo.it (tgioc.prometeo.it [194.21.36.34]) by prometeo.prometeo.it (8.6.12/8.6.12) with ESMTP id SAA03945; Thu, 8 Aug 1996 18:34:46 +0200 Message-Id: <199608081634.SAA03945@prometeo.prometeo.it> Reply-To: From: "COI Giovanni" To: , , Subject: Hitachi CD-ROM ATAPI problem Date: Thu, 8 Aug 1996 18:29:11 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1132 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello. I have to install a FreeBSD system on a PCI Pentium/133, 32 Mbyte RAM, HD 1.2 Gbyte and a Hitachi CD-ROM ATAPI. The release that I have installad is 2.1.5-stable (from mirror www.se.FreeBSD.org at August 6 1996). The problem is the CD-ROM. It is set as Master into the second IDE controller with the hard drive set as Master into the first IDE controller. When start (with a CD into the unit) the initial hardware test show: FreeBSD 2.1.5-RELEASE #0: Thu Aug 8 17:01:59 MET DST 1996 root@prometeo.it:/usr/src/sys/compile/PROM586b CPU: 133-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30699520 (29980K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 0 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 72 int a irq 11 on pci0:9 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> ed0 at 0x340-0x35f irq 5 on isa ed0: address 00:00:1b:3a:8f:3f, type NE2000 (16 bit) lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, iordy wcd0: 689Kb/sec, 128Kb cache, audio play, 128 volume levels, ejectable tray wcd0: medium type unknown, unlocked fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface --------------------------------------------------- So it find correctly two units. (NB. If CD-ROM do not set as Master in second IDE it missing from the probe log. If it is set as Salve in first IDE the system do not boot at all. It don't find any bootable units.) When from root's shell I type: mount -t cd9660 /dev/wcd0c /mnt the system relply: cd9660: /dev/wcd0c: Device not configured Do you have any brilliant suggestions that may aid me in my search for the perfectly functional FreeBSD system? I would appreciate any comments that you could email to me. ---------------------------------------------------------- Prometeo srl - Progetti e Metodologie Informatiche Internet Services Provider Coi Giovanni Voice : +39(0)41 5701366 Via Taglio Sinistro 61/B Fax : +39(0)41 5701005 30035 MIRANO (VE) - ITALY e-mail: coi@prometeo.it http://www.prometeo.it