From owner-freebsd-questions Fri Aug 14 09:44:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23421 for freebsd-questions-outgoing; Fri, 14 Aug 1998 09:44:25 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from nss4.cc.Lehigh.EDU (nss4.CC.Lehigh.EDU [128.180.1.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23388 for ; Fri, 14 Aug 1998 09:44:18 -0700 (PDT) (envelope-from ase2@lehigh.edu) Received: from ns2-1.CC.Lehigh.EDU (ase2@ns2-1.CC.Lehigh.EDU [128.180.1.33]) by nss4.cc.Lehigh.EDU (8.8.8/8.8.5) with ESMTP id MAA33544 for ; Fri, 14 Aug 1998 12:43:43 -0400 From: ALI SAIT ERKAN Received: (from ase2@localhost) by ns2-1.CC.Lehigh.EDU (8.8.5/8.8.5) id MAA55126 for questions@freebsd.org; Fri, 14 Aug 1998 12:43:45 -0400 Date: Fri, 14 Aug 1998 12:43:45 -0400 Message-Id: <199808141643.MAA55126@ns2-1.CC.Lehigh.EDU> To: questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, We are in the process of converting a few of our key machines in our lab to FreeBSD. We have encountered a number of problems: [1] Two of our machines (say A and B) are dual interfaced (the -i interfaces are 10BaseT and the -ii interfaces are 100BaseT): A-i <---10BaseT---> B-i A-ii <--100BaseT---> B-ii When A and B talk over the 10BaseT interfaces, things are ok :) When they use their 100BaseT interfaces, thing are not ok :( With large NFS transfers, the client seems to hang. With smaller transfers, some threshold related messages are syslog'ed yet the transfer appears to complete. [2] Bringing an interface down and then up does not seem to work. Also, if a network cable is disconnected for a second and then reconnected immediately, the associated interface cannot be used (again bringing it down and then up does not work). [3] For someone who has been spoiled by the LDP and all related printed material, are there any FreeBSD administration books out there? Thanks in advance. ------------------------------------------------------------------------------- Here is the relevant info: uname -a FreeBSD ball 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Thu Aug 13 09:18:36 EDT 1998 root@:/usr/src/sys/compile/BALL i386 interfaces: (Used at 10mb/s) de0 rev 48 int a irq 5 on pci0:10:0 de0: 21143 [10-100Mb/s] pass 3.0 de0: address 00:48:54:00:1b:97 (Used at 100mb/s) de1 rev 48 int a irq 9 on pci0:12:0 de1: 21143 [10-100Mb/s] pass 3.0 de1: address 00:48:54:00:13:a1 (Used at 10mb/s) de2 rev 34 int a irq 10 on pci0:14:0 de2: 21140A [10-100Mb/s] pass 2.2 de2: address 00:40:05:41:aa:d3 /var/log/messages Aug 14 10:17:19 ball /kernel: de0: enabling 10baseT port Aug 14 10:17:19 ball /kernel: de1: enabling 100baseTX port Aug 14 10:17:19 ball /kernel: de2: enabling 10baseT port Aug 14 10:17:29 ball login: ROOT LOGIN (root) ON ttyv0 Aug 14 10:18:37 ball /kernel: de1: receive: 00:48:54:00:0d:5b: bad crc Aug 14 10:18:40 ball /kernel: de1: receive: 00:48:54:00:0d:5b: bad crc Aug 14 10:20:05 ball /kernel: de1: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) Aug 14 10:20:06 ball /kernel: de1: abnormal interrupt: transmit underflow (raising TX threshold to 8|512) Aug 14 10:20:09 ball /kernel: de1: abnormal interrupt: transmit underflow (raising TX threshold to 1024) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message