From owner-freebsd-bugs@FreeBSD.ORG Sat Feb 24 09:00:20 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6116916A403 for ; Sat, 24 Feb 2007 09:00:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 0A94913C442 for ; Sat, 24 Feb 2007 09:00:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1O90J9Y014357 for ; Sat, 24 Feb 2007 09:00:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1O90Jrf014353; Sat, 24 Feb 2007 09:00:19 GMT (envelope-from gnats) Date: Sat, 24 Feb 2007 09:00:19 GMT Message-Id: <200702240900.l1O90Jrf014353@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Remko Lodder Cc: Subject: Re: misc/109477: onboard via vt6103 ethernet does not work X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Remko Lodder List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Feb 2007 09:00:20 -0000 The following reply was made to PR kern/109477; it has been noted by GNATS. From: Remko Lodder To: Burkhard Steding Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/109477: onboard via vt6103 ethernet does not work Date: Sat, 24 Feb 2007 09:54:42 +0100 >> Description: > Feb 23 20:55:50 kernel: vr0: port 0xee00-0xe > eff mem 0xdfffd000-0xdfffd0ff irq 23 at device 18.0 on pci0 > Feb 23 20:55:50 kernel: miibus0: on vr0 > > and, somewhat later: > > Feb 23 20:55:54 kernel: vr0: watchdog timeout > > I can do a "ping 192.168.42.21" but I can not reach any other machine on the subnet. I have verified that it's neither a hardware nor a cable problem. It works fine with a NetBSD installation. By the way, the FreeBSD and the NetBSD if_vr.c driver are derived from the same original source, but have evolved since then. > > I have build a custom kernel specific for my hardware with if_vr.ko as a loadable module and I am willing to assist in bug fixing, if my time allows. I have some experience in writing a device driver but do not know anything about the via rhine chips. > >> How-To-Repeat: > The problem can easyly be repeated both with the GENERIC kernel and a custom kernel that uses if_vr.ko as a loadable module. Then the messages show up after "kldload if_vr.ko". >> Fix: Hello, Now that is interesting, I happen to have the exact same ethernet card onboard of my motherboard: redqueen# cat /var/run/dmesg.boot | grep vr vr0: port 0x7400-0x74ff mem 0xf0000000-0xf00000ff at device 18.0 on pci0 miibus0: on vr0 vr0: Ethernet address: 00:0c:6e:8d:88:ad I am using this for like two years now without a problem. Can you tell me whether you see traffic passing over the vr0 card at all? (tcpdump -n -i vr0 would give information about that), do you see arp adresses being exchanged? What happends when you try to setup traffic towards another host? What do you have installed on your system? (anything of these might prevent your data other then ping, being blocked)... Hope to see your answers soon! Cheers, Remko -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */