From owner-freebsd-current@FreeBSD.ORG Fri Jun 12 20:30:35 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BF3D106568D for ; Fri, 12 Jun 2009 20:30:35 +0000 (UTC) (envelope-from thomas+freebsd@lotterer.net) Received: from angel.hellmouth.lotterer.net (angel.hellmouth.lotterer.net [88.198.53.82]) by mx1.freebsd.org (Postfix) with ESMTP id EDEF88FC1A for ; Fri, 12 Jun 2009 20:30:34 +0000 (UTC) (envelope-from thomas+freebsd@lotterer.net) Received: from dawn.sunnydale.lotterer.net (ppp-93-104-163-93.dynamic.mnet-online.de [93.104.163.93]) by angel.hellmouth.lotterer.net (Postfix) with ESMTPS id 3E4071EC102; Fri, 12 Jun 2009 22:30:33 +0200 (CEST) Received: from [172.17.16.148] (lab-winxp-1.sunnydale.lotterer.net [172.17.16.148]) by dawn.sunnydale.lotterer.net (Postfix) with ESMTPSA id 706D847A6F; Fri, 12 Jun 2009 22:30:33 +0200 (CEST) Message-ID: <4A32BAE7.40605@lotterer.net> Date: Fri, 12 Jun 2009 22:30:31 +0200 From: Thomas Lotterer User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: pyunyh@gmail.com References: <4A2DA8D9.2030300@lotterer.net> <20090610024959.GD63941@michelle.cdnetworks.co.kr> <4A2FF8E3.4060501@lotterer.net> <20090611002923.GA68519@michelle.cdnetworks.co.kr> <4A30FD94.4030409@lotterer.net> <20090611130557.GB68519@michelle.cdnetworks.co.kr> <4A312517.9030206@lotterer.net> <20090612055032.GD72855@michelle.cdnetworks.co.kr> In-Reply-To: <20090612055032.GD72855@michelle.cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.2.5-openpkg X-Spam-Checker-Version: SpamAssassin 3.2.5-openpkg (2008-06-10) on angel.lotterer.net Cc: freebsd-current@freebsd.org Subject: Re: suspect bug in vge(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 20:30:36 -0000 Pyun YongHyeon wrote: > On Thu, Jun 11, 2009 at 05:39:03PM +0200, Thomas Lotterer wrote: >> Pyun YongHyeon wrote: >>> Could you show me dmesg output(only vge(4) related one)? >>> >> # dmesg | grep vge >> vge0: port 0xec00-0xecff mem >> 0xdf7ff000-0xdf7ff0ff irq 28 at device 0.0 on pci2 >> vge0: MSIX count : 0 >> vge0: MSI count : 1 > > I wonder why "Using 1 MSI messages" message is missing. > Never seen that message. Maybe more verbose/debug needed? OK, next round. Here are today's findings. I switched from statically linked to dynamically loaded drivers to accelerate the build+test process. Finally, the results with both vge(4) drivers dynamically loaded and statically linked were the same. The good news is that the "yongari" driver actually works in one of three or four cases. The situation with the driver when auto detecting GigE is as already described: >> # ifconfig vge0 >> vge0: flags=8843 metric 0 mtu 1500 >> options=389b >> ether 00:40:63:xx:xx:xx >> inet [...] >> media: Ethernet autoselect (1000baseT ) >> status: active >> >> Unfortunately, no traffic could be sent and tcpdump(1) does not show any >> incoming packages either, not even broadcasts. However, sometimes the driver (incorrectly) auto selects 100BaseTX media: Ethernet autoselect (100baseTX ) in which case it works well. I was able to copy 1500MB of data from the server and back in three parallel running CIFS connections. The "original problem" driver always broke upload before 100MB barrier. >> Interesting side effect is that after that test the kernel with my >> previous "original problem" vge(4) driver rebooted when initializing the >> network card. No logs at this stage, sorry. Reboot did not help. Hard >> reset did not help. Power cycle did help. Behavior was reproducible on a >> second attempt. My experience after countless reboots is that both drivers always show this problem after the "yongari" driver was loaded previously. However, enabling "boot from VIA Ethernet" in BIOS has been found to be a better and more reliable workaround than power cycling. Not that I want to boot from the network, it just seems the BIOS is resetting the NIC properly. Also I was able to capture the error log from the screen: vge0: port 0xec00-0xecff mem 0xdf7ff000-0xdf7ff0ff irg 11 at device 0.0 on pci2 vge0: MII read timed out vge0: failed to start MII autopoll vge0: MII without any phy! panic: Assertion mtx_unowned(m) failed at /usr/src/sys/kern/kern_mutex.c:827 Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting ... -- http://thomas.lotterer.net