From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 04:00:02 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8146C16A4CF for ; Sun, 28 Dec 2003 04:00:02 -0800 (PST) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BD5943D4C for ; Sun, 28 Dec 2003 03:59:44 -0800 (PST) (envelope-from yamamoto436@oki.com) Received: from aoi.okilab.oki.co.jp (localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id UAA21366 for ; Sun, 28 Dec 2003 20:59:42 +0900 Received: (qmail 30863 invoked from network); 28 Dec 2003 20:59:41 +0900 Received: from tulip.okilab.oki.co.jp (172.24.23.187) by aoi.okilab.oki.co.jp with SMTP; 28 Dec 2003 20:59:41 +0900 Received: from localhost (tulip [172.24.23.187])hBSC1qG5068569 for ; Sun, 28 Dec 2003 21:01:52 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Sun, 28 Dec 2003 21:01:52 +0900 (JST) Message-Id: <20031228.210152.74688241.yamamoto436@oki.com> To: stable@freebsd.org From: Hideki Yamamoto In-Reply-To: <3EDE1B6A.6050804@isometry.net> References: <3EDE1B6A.6050804@isometry.net> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: bge drivers does not work for 3COM 3C996-SX / 3C996B-T X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2003 12:00:02 -0000 Hi, I tried today's 4.9-stable on a FreeBSD box with two 3COM 3C996-SXs and two onboard BMC5703 chips. 3COM 3C996-SX boards are linkup, but the other side, an SX I/F on SUN F280 is not linkup. When doing ping command to SUN, LED on 3C996 are brinking but nothing happens to SUN board. I changed bge0 to bge2, but the situation is the same. Hardware diagram is as follows. bge0 can connect to the router or another PC with intel SX board. Is this related to AUTO negotiation? I cannot find any parameters about AUTO negotiation in 'bge' driver source. Any help would be greatly appreciated. Hideki Yamamoto +--------------+ | | | (bge0)3C996-SX+-----+[Router] | | | (bge2)3C996-SX+-----+[SUN F280] | | +--------------+ bge0: mem 0xf7ef0000-0xf7efffff irq 10 at device 1.0 on pci1 bge0: Ethernet address: 00:04:76:e1:06:cf bge1: mem 0xf7ee0000-0xf7eeffff irq 11 at device 2.0 on pci1 bge1: Ethernet address: 00:0b:cd:d2:b0:40 miibus0: on bge1 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto pcib2: on motherboard pci2: on pcib2 pcib3: on motherboard pci3: on pcib3 pcib4: on motherboard IOAPIC #1 intpin 10 -> irq 15 IOAPIC #1 intpin 13 -> irq 16 pci4: on pcib4 bge2: mem 0xf7ff0000-0xf7ffffff irq 15 at device 1.0 on pci4 bge2: Ethernet address: 00:0a:5e:1d:83:25 bge3: mem 0xf7fe0000-0xf7feffff irq 16 at device 2.0 on pci4 bge3: Ethernet address: 00:0b:cd:d2:b0:3b ----------------------------------------------------------------- Hideki YAMAMOTO Oki Electric Industry Co., Ltd. From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 04:20:48 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5732A16A4CF for ; Sun, 28 Dec 2003 04:20:48 -0800 (PST) Received: from sis1.snu.ac.kr (sis1.snu.ac.kr [147.46.10.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C85443D48 for ; Sun, 28 Dec 2003 04:20:45 -0800 (PST) (envelope-from nospam@users.sourceforge.net) Received: from users.sourceforge.net ([147.46.44.183]) by sis1.snu.ac.kr (8.12.10/8.12.10) with ESMTP id hBSCI61i242662 for ; Sun, 28 Dec 2003 21:18:06 +0900 Message-ID: <3FEECA99.4030603@users.sourceforge.net> Date: Sun, 28 Dec 2003 21:20:41 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031104 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: NFS problem: "RPC: Port mapper failure" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2003 12:20:48 -0000 Hi, I am running two FreeBSD-Stable PCs. One is an NFS server and the other NFS client. Everything used to work fine until recently. I suspect that either the new kernel is the problem (although there are no complaints on the stable mailing list) or the network administration has changed some things. The server is on 147.46.44.183 with following /etc/exports: /usr/ports -maproot=root 147.47.254.184 /home/entertainment -ro 147.47.254.184 The server boots with rc.conf: nfs_reserved_port_only="YES" portmap_enable="YES" nfs_server_enable="YES" mountd_flags="-r" The client boots with rc.conf: nfs_reserved_port_only="YES" nfs_client_enable="YES" On the client (147.47.254.184) I do not get the proper response on: $ showmount -e 147.46.44.183 RPC: Port mapper failure showmount: can't do exports rpc Doing a mount_nfs on the client, gives the same port mapper failure. Portmap is running on the server; it is not on the client, but that should be OK here, right? I am at a total loss, since I have no idea how to investigate further what is actually going wrong. What could be a reason for the RPC Port mapper failure? How else can I test the port mapper's functunality? Thanks, Rob. From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 19:43:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDFB016A4CE for ; Sun, 28 Dec 2003 19:43:27 -0800 (PST) Received: from doom.homeunix.org (8-248.dialup.comset.net [213.172.8.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69DC943D55 for ; Sun, 28 Dec 2003 19:43:03 -0800 (PST) (envelope-from igor@doom.homeunix.org) Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.12.10/8.12.10) with ESMTP id hBT3gTAT000749; Mon, 29 Dec 2003 06:42:36 +0300 (MSK) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.12.10/8.12.10/Submit) id hBT3gLaQ000748; Mon, 29 Dec 2003 06:42:21 +0300 (MSK) (envelope-from igor) Date: Mon, 29 Dec 2003 06:42:21 +0300 From: Igor Pokrovsky To: Rob Message-ID: <20031229034221.GA671@doom.homeunix.org> Mail-Followup-To: Rob , freebsd-stable@freebsd.org References: <3FEECA99.4030603@users.sourceforge.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FEECA99.4030603@users.sourceforge.net> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: NFS problem: "RPC: Port mapper failure" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 03:43:28 -0000 On Sun, Dec 28, 2003 at 09:20:41PM +0900, Rob wrote: > > Hi, > > I am running two FreeBSD-Stable PCs. > > One is an NFS server and the other NFS client. Everything used to > work fine until recently. I suspect that either the new kernel is the > problem (although there are no complaints on the stable mailing list) > or the network administration has changed some things. > > The server is on 147.46.44.183 with following /etc/exports: > /usr/ports -maproot=root 147.47.254.184 > /home/entertainment -ro 147.47.254.184 > > The server boots with rc.conf: > nfs_reserved_port_only="YES" > portmap_enable="YES" > nfs_server_enable="YES" > mountd_flags="-r" > > The client boots with rc.conf: > nfs_reserved_port_only="YES" > nfs_client_enable="YES" > > On the client (147.47.254.184) I do not get the proper response on: > $ showmount -e 147.46.44.183 > RPC: Port mapper failure > showmount: can't do exports rpc > > Doing a mount_nfs on the client, gives the same port mapper failure. > > Portmap is running on the server; it is not on the client, but > that should be OK here, right? > > I am at a total loss, since I have no idea how to investigate further > what is actually going wrong. What could be a reason for the RPC Port > mapper failure? How else can I test the port mapper's functunality? You can try to check if nfsd and portmap really started on server: sockstat | grep portmap and sockstat | grep nfsd -ip -- "Well," Brahma said, "even after ten thousand explanations, a fool is no wiser, but an intelligent man requires only two thousand five hundred." -- The Mahabharata. From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 20:59:53 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A79D716A4CE for ; Sun, 28 Dec 2003 20:59:53 -0800 (PST) Received: from obie.softweyr.com (66-91-236-204.san.rr.com [66.91.236.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id D201143D1F for ; Sun, 28 Dec 2003 20:59:49 -0800 (PST) (envelope-from wes@softweyr.com) Received: from zahpod.softweyr.com (8bdbd7199d820c02dc885b1557323a61@zaphod [204.68.178.5]) by obie.softweyr.com (8.12.10/8.12.10) with ESMTP id hBT4xm5i019411; Sun, 28 Dec 2003 20:59:48 -0800 (PST) (envelope-from wes@softweyr.com) From: Wes Peters Organization: Softweyr To: Hideki Yamamoto , stable@freebsd.org Date: Sun, 28 Dec 2003 20:59:47 -0800 User-Agent: KMail/1.5.4 References: <3EDE1B6A.6050804@isometry.net> <20031228.210152.74688241.yamamoto436@oki.com> In-Reply-To: <20031228.210152.74688241.yamamoto436@oki.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312282059.47990.wes@softweyr.com> Subject: Re: bge drivers does not work for 3COM 3C996-SX / 3C996B-T X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 04:59:53 -0000 On Sunday 28 December 2003 04:01 am, Hideki Yamamoto wrote: > Hi, > > I tried today's 4.9-stable on a FreeBSD box with two 3COM 3C996-SXs and > two onboard BMC5703 chips. 3COM 3C996-SX boards are linkup, but the > other side, an SX I/F on SUN F280 is not linkup. > When doing ping command to SUN, LED on 3C996 are brinking but > nothing happens to SUN board. > I changed bge0 to bge2, but the situation is the same. > Hardware diagram is as follows. bge0 can connect to the router or > another PC with intel SX board. > Is this related to AUTO negotiation? I cannot find any parameters > about AUTO negotiation in 'bge' driver source. > > Any help would be greatly appreciated. > > Hideki Yamamoto > > +--------------+ > > | (bge0)3C996-SX+-----+[Router] > | > | (bge2)3C996-SX+-----+[SUN F280] > > +--------------+ > > bge0: mem > 0xf7ef0000-0xf7efffff irq 10 at device 1.0 on pci1 bge0: Ethernet > address: 00:04:76:e1:06:cf No miibus or PHY on bge0? > bge1: mem > 0xf7ee0000-0xf7eeffff irq 11 at device 2.0 on pci1 bge1: Ethernet > address: 00:0b:cd:d2:b0:40 > miibus0: on bge1 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto pcib2: on motherboard Apparently this is a copper (1000baseTX) card, right? > bge2: mem > 0xf7ff0000-0xf7ffffff irq 15 at device 1.0 on pci4 bge2: Ethernet > address: 00:0a:5e:1d:83:25 > bge3: mem > 0xf7fe0000-0xf7feffff irq 16 at device 2.0 on pci4 bge3: Ethernet > address: 00:0b:cd:d2:b0:3b Again, no miibus or PHY on bge2 and bge3? Are these both SX cards? -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 21:01:00 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F020916A4CF for ; Sun, 28 Dec 2003 21:01:00 -0800 (PST) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ECC043D31 for ; Sun, 28 Dec 2003 21:00:59 -0800 (PST) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smtp3.sentex.ca (8.12.10/8.12.10) with ESMTP id hBT50uHF062080; Mon, 29 Dec 2003 00:00:56 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9p2/8.12.9) with ESMTP id hBT50tXw031201; Mon, 29 Dec 2003 00:00:56 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.0.1.1.0.20031228235455.07f72da0@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Mon, 29 Dec 2003 00:00:08 -0500 To: Vinod Kashyap , stable@freebsd.org From: Mike Tancsa In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Subject: RE: official 3ware support ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 05:01:01 -0000 At 01:55 PM 24/12/2003, Vinod Kashyap wrote: >Yes, 3ware now supports FreeBSD! > >The driver you find on the 3ware website has been >extensively tested on 4.8, and not yet on 4.9. Hi, I was just playing around with your beta driver on 4.9 STABLE. Am I safe to assume that if I dont have PAE enabled and have <=2G of RAM installed, the driver should work ? Also, will there be an updated 3dmd ? Thanks for officially supporting FreeBSD! ---Mike >The changes in this driver should soon make their >way into RELENG_4. They are already checked into HEAD. > > >Thanks, > >Vinod. > > >-----Original Message----- >From: Mike Tancsa [mailto:mike@sentex.net] >Sent: Wednesday, December 24, 2003 8:48 AM >To: stable@freebsd.org >Cc: ps@freebsd.org >Subject: official 3ware support ? > > > >While looking for firmware updates on the 3ware site, I notice they now >have FreeBSD drivers available for download marked as "beta" > >The readme with the drivers download says, > >"This directory contains the 3ware driver (twe.ko) for 7000 series >storage controllers, and the corresponding source code. The latest >source code can be downloaded from the freebsd kernel tree, by running >cvsup. >The source code can be found at: >http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/twe >http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twe >" > >However, what is in RELENG_4 differs from what is downloaded from the 3ware >site. > >Also, its marked 4.8. Will it work with 4.9 which has all the PAE changes >in it? > > ---Mike >-------------------------------------------------------------------- >Mike Tancsa, tel +1 519 651 3400 >Sentex Communications, mike@sentex.net >Providing Internet since 1994 www.sentex.net >Cambridge, Ontario Canada www.sentex.net/mike > >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > >DISCLAIMER: The information contained in this electronic mail transmission >is intended by 3ware for the use of the named individual or entity to which >it is directed and may contain information that is confidential or >privileged and should not be disseminated without prior approval from 3ware From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 21:13:11 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0EAB16A4CE for ; Sun, 28 Dec 2003 21:13:11 -0800 (PST) Received: from eden.barryp.org (host-150-32-220-24.midco.net [24.220.32.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44F7D43D49 for ; Sun, 28 Dec 2003 21:13:10 -0800 (PST) (envelope-from bp@barryp.org) Received: from [10.66.0.234] (helo=barryp.org) by eden.barryp.org with asmtp (Exim 4.20) id 1AapiD-000MfZ-SJ; Sun, 28 Dec 2003 23:13:05 -0600 Message-ID: <3FEFB7E0.60003@barryp.org> Date: Sun, 28 Dec 2003 23:13:04 -0600 From: Barry Pederson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031020 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org References: <6.0.1.1.0.20031228235455.07f72da0@209.112.4.2> In-Reply-To: <6.0.1.1.0.20031228235455.07f72da0@209.112.4.2> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on eden.barryp.org X-Spam-Status: No, hits=-4.9 required=4.5 tests=BAYES_00 autolearn=ham version=2.61 cc: Vinod Kashyap Subject: Re: official 3ware support ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 05:13:12 -0000 Mike Tancsa wrote: > At 01:55 PM 24/12/2003, Vinod Kashyap wrote: > >> Yes, 3ware now supports FreeBSD! >> >> The driver you find on the 3ware website has been >> extensively tested on 4.8, and not yet on 4.9. > > > Hi, > I was just playing around with your beta driver on 4.9 STABLE. > Am I safe to assume that if I dont have PAE enabled and have <=2G of RAM > installed, the driver should work ? Also, will there be an updated 3dmd ? I was wondering about 3dmd support too, especially on FreeBSD 5.x. The last time I tried it, on a 5.1-Release box, you had to apply a binary patch to make it work, as described in this old message from the freebsd-current list. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1035474+0+archive/2003/freebsd-current/20030601.freebsd-current It's kind of an ugly process to have to go through. Barry From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 21:39:35 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1640516A4CE for ; Sun, 28 Dec 2003 21:39:35 -0800 (PST) Received: from sis1.snu.ac.kr (sis1.snu.ac.kr [147.46.10.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DF7843D45 for ; Sun, 28 Dec 2003 21:39:33 -0800 (PST) (envelope-from nospam@users.sourceforge.net) Received: from users.sourceforge.net ([147.46.44.183]) by sis1.snu.ac.kr (8.12.10/8.12.10) with ESMTP id hBT5JI1i231408 for ; Mon, 29 Dec 2003 14:19:18 +0900 Message-ID: <3FEFB9F4.7060500@users.sourceforge.net> Date: Mon, 29 Dec 2003 14:21:56 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031104 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <3FEECA99.4030603@users.sourceforge.net> <20031229034221.GA671@doom.homeunix.org> In-Reply-To: <20031229034221.GA671@doom.homeunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: NFS problem: "RPC: Port mapper failure" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 05:39:35 -0000 Igor Pokrovsky wrote: > On Sun, Dec 28, 2003 at 09:20:41PM +0900, Rob wrote: > >>Hi, >> >>I am running two FreeBSD-Stable PCs. >> >>One is an NFS server and the other NFS client. Everything used to >>work fine until recently. I suspect that either the new kernel is the >>problem (although there are no complaints on the stable mailing list) >>or the network administration has changed some things. > > You can try to check if nfsd and portmap really started on server: > sockstat | grep portmap > and > sockstat | grep nfsd This is what I get. The NFS server is 147.46.44.183 with gateway 147.46.44.1 The NFS client is 147.47.254.184 with gateway 147.47.254.1 On the NFS server: $ sockstat | grep portmap daemon portmap 79693 3 udp4 *:111 *:* daemon portmap 79693 4 tcp4 *:111 *:* $ sockstat | grep nfsd root nfsd 87 3 tcp4 *:2049 *:* $ sockstat | grep mount root mountd 84 3 udp4 *:1023 *:* root mountd 84 4 tcp4 *:1023 *:* On the client: $ rpcinfo -p 147.46.44.183 rpcinfo: can't contact portmapper: RPC: Remote system error - Operation timed out On another computer with the same gateway as the server: $ rpcinfo -p 147.46.44.183 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper Any idea what could block the contact to the portmapper? Could a network setup at one of the gateways cause these trouble, such as a firewall (though I don't know anything about firewalls!) ? Secure shell connections still work fine between all the computers! Thanks for your help. Rob. From owner-freebsd-stable@FreeBSD.ORG Mon Dec 29 01:41:51 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07B4816A4CE for ; Mon, 29 Dec 2003 01:41:51 -0800 (PST) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5689943D31 for ; Mon, 29 Dec 2003 01:40:33 -0800 (PST) (envelope-from yamamoto436@oki.com) Received: from aoi.okilab.oki.co.jp (localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id SAA05561 for ; Mon, 29 Dec 2003 18:40:08 +0900 Received: (qmail 24013 invoked from network); 29 Dec 2003 18:40:07 +0900 Received: from tulip.okilab.oki.co.jp (172.24.23.187) by aoi.okilab.oki.co.jp with SMTP; 29 Dec 2003 18:40:07 +0900 Received: from localhost (tulip [172.24.23.187])hBT9g7G5070946; Mon, 29 Dec 2003 18:42:32 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Mon, 29 Dec 2003 18:42:07 +0900 (JST) Message-Id: <20031229.184207.74681106.yamamoto436@oki.com> To: wes@softweyr.com From: Hideki Yamamoto In-Reply-To: <200312282059.47990.wes@softweyr.com> References: <3EDE1B6A.6050804@isometry.net> <20031228.210152.74688241.yamamoto436@oki.com> <200312282059.47990.wes@softweyr.com> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: bge drivers does not work for 3COM 3C996-SX / 3C996B-T X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 09:41:51 -0000 Dear Paters, Thank you for your reply. From: Wes Peters Subject: Re: bge drivers does not work for 3COM 3C996-SX / 3C996B-T Date: Sun, 28 Dec 2003 20:59:47 -0800 Message-ID: <200312282059.47990.wes@softweyr.com> > On Sunday 28 December 2003 04:01 am, Hideki Yamamoto wrote: > > Hi, > > > > I tried today's 4.9-stable on a FreeBSD box with two 3COM 3C996-SXs and > > two onboard BMC5703 chips. 3COM 3C996-SX boards are linkup, but the > > other side, an SX I/F on SUN F280 is not linkup. > > When doing ping command to SUN, LED on 3C996 are brinking but > > nothing happens to SUN board. > > I changed bge0 to bge2, but the situation is the same. > > Hardware diagram is as follows. bge0 can connect to the router or > > another PC with intel SX board. > > Is this related to AUTO negotiation? I cannot find any parameters > > about AUTO negotiation in 'bge' driver source. > > > > Any help would be greatly appreciated. > > > > Hideki Yamamoto > > > > +--------------+ > > > > | (bge0)3C996-SX+-----+[Router] > > | > > | (bge2)3C996-SX+-----+[SUN F280] > > > > +--------------+ > > > > bge0: mem > > 0xf7ef0000-0xf7efffff irq 10 at device 1.0 on pci1 bge0: Ethernet > > address: 00:04:76:e1:06:cf > > No miibus or PHY on bge0? Sorry, I cannot answer because my knowledge is not sufficient. > > bge1: mem > > 0xf7ee0000-0xf7eeffff irq 11 at device 2.0 on pci1 bge1: Ethernet > > address: 00:0b:cd:d2:b0:40 > > miibus0: on bge1 > > brgphy0: on miibus0 > > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > > 1000baseTX-FDX, auto pcib2: on motherboard > > Apparently this is a copper (1000baseTX) card, right? Yes. Both bge1 and bge3 are onboard 1000/100/10base copper cards. These are based on BCM5703. Both bge0 and bge2 are SX cards. > > bge2: mem > > 0xf7ff0000-0xf7ffffff irq 15 at device 1.0 on pci4 bge2: Ethernet > > address: 00:0a:5e:1d:83:25 > > bge3: mem > > 0xf7fe0000-0xf7feffff irq 16 at device 2.0 on pci4 bge3: Ethernet > > address: 00:0b:cd:d2:b0:3b > > Again, no miibus or PHY on bge2 and bge3? Are these both SX cards? Would you tell me how to gathere additional information? > Where am I, and what am I doing in this handbasket? > > Wes Peters wes@softweyr.com > Regards, Hideki Yamamoto From owner-freebsd-stable@FreeBSD.ORG Mon Dec 29 02:13:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3F0016A4CE for ; Mon, 29 Dec 2003 02:13:55 -0800 (PST) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EED343D1F for ; Mon, 29 Dec 2003 02:13:52 -0800 (PST) (envelope-from yamamoto436@oki.com) Received: from aoi.okilab.oki.co.jp (localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id TAA09322 for ; Mon, 29 Dec 2003 19:13:50 +0900 Received: (qmail 25373 invoked from network); 29 Dec 2003 19:13:49 +0900 Received: from tulip.okilab.oki.co.jp (172.24.23.187) by aoi.okilab.oki.co.jp with SMTP; 29 Dec 2003 19:13:49 +0900 Received: from localhost (tulip [172.24.23.187])hBTAGFG5071049; Mon, 29 Dec 2003 19:16:15 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Mon, 29 Dec 2003 19:16:15 +0900 (JST) Message-Id: <20031229.191615.71155718.yamamoto436@oki.com> To: wes@softweyr.com From: Hideki Yamamoto In-Reply-To: <20031229.184207.74681106.yamamoto436@oki.com> References: <20031228.210152.74688241.yamamoto436@oki.com> <200312282059.47990.wes@softweyr.com> <20031229.184207.74681106.yamamoto436@oki.com> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: bge drivers does not work for 3COM 3C996-SX / 3C996B-T X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 10:13:55 -0000 Dear Peters > > > > > > bge0: mem > > > 0xf7ef0000-0xf7efffff irq 10 at device 1.0 on pci1 bge0: Ethernet > > > address: 00:04:76:e1:06:cf > > > > No miibus or PHY on bge0? > > Sorry, I cannot answer because my knowledge is not sufficient. Neither PHY nor miibus exist on bge0 and bge2. Both bge0 and bge2 are SX cards. The following is the full dmesg. bge1 and bge3 have miibus and phy. ------------------------------------------------------------ Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-STABLE #0: Sun Dec 28 17:21:50 JST 2003 vod@tsrmldgw1:/usr/obj/usr/src/sys/mldgw Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3065.81-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1610588160 (1572840K bytes) avail memory = 1562906624 (1526276K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 Programming 16 pins in IOAPIC #2 Programming 16 pins in IOAPIC #3 FreeBSD/SMP: Multiprocessor motherboard: 4 CPUs cpu0 (BSP): apic id: 6, version: 0x00050014, at 0xfee00000 cpu1 (AP): apic id: 7, version: 0x00050014, at 0xfee00000 cpu2 (AP): apic id: 0, version: 0x00050014, at 0xfee00000 cpu3 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec01000 io2 (APIC): apic id: 4, version: 0x000f0011, at 0xfec02000 io3 (APIC): apic id: 5, version: 0x000f0011, at 0xfec03000 Preloaded elf kernel "kernel" at 0xc0430000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #1 intpin 15 -> irq 2 IOAPIC #1 intpin 7 -> irq 3 IOAPIC #1 intpin 6 -> irq 5 IOAPIC #0 intpin 10 -> irq 7 pci0: on pcib0 pci0: at 3.0 ciss0: port 0x2800-0x28ff mem 0xf5df0000-0xf5df3fff,0xf5f80000-0xf5fbffff irq 2 at device 4.0 on pci0 pci0: (vendor=0x0e11, dev=0xb203) at 5.0 irq 3 pci0: (vendor=0x0e11, dev=0xb204) at 5.2 irq 5 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x2000-0x200f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ohci0: mem 0xf5e70000-0xf5e70fff irq 7 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: on motherboard IOAPIC #1 intpin 12 -> irq 10 IOAPIC #1 intpin 14 -> irq 11 pci1: on pcib1 bge0: mem 0xf7ef0000-0xf7efffff irq 10 at device 1.0 on pci1 bge0: Ethernet address: 00:04:76:e1:06:cf bge1: mem 0xf7ee0000-0xf7eeffff irq 11 at device 2.0 on pci1 bge1: Ethernet address: 00:0b:cd:d2:b0:40 miibus0: on bge1 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto pcib2: on motherboard pci2: on pcib2 pcib3: on motherboard pci3: on pcib3 pcib4: on motherboard IOAPIC #1 intpin 10 -> irq 15 IOAPIC #1 intpin 13 -> irq 16 pci4: on pcib4 bge2: mem 0xf7ff0000-0xf7ffffff irq 15 at device 1.0 on pci4 bge2: Ethernet address: 00:0a:5e:1d:83:25 bge3: mem 0xf7fe0000-0xf7feffff irq 16 at device 2.0 on pci4 bge3: Ethernet address: 00:0b:cd:d2:b0:3b miibus1: on bge3 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto pcib5: on motherboard pci5: on pcib5 eisa0: on motherboard mainboard0: on eisa0 slot 0 eisa0: unknown card Z@B0000 (0x68020000) at slot 2 orm0: