From owner-freebsd-current@FreeBSD.ORG Fri Jun 12 05:47:49 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 D69E5106566C for ; Fri, 12 Jun 2009 05:47:49 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f197.google.com (mail-pz0-f197.google.com [209.85.222.197]) by mx1.freebsd.org (Postfix) with ESMTP id A17CB8FC14 for ; Fri, 12 Jun 2009 05:47:49 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pz0-f197.google.com with SMTP id 35so1150923pzk.3 for ; Thu, 11 Jun 2009 22:47:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=2lL8hvx3FKt+0vzAtTRMmPgY0EZ+ZJTc11Nj1PwmHKI=; b=Vp3S822bW6QlTvuJrpsL1hXGAmpOeHLw4m6XRvoz821aFxaby8D8wOgRXbr09A94QV JoLuRqDrTG2EE8sn0OiLLMWhEYlfyqUcr2EEKNueC3IjXsF8LMIHeKcvnv+YeH+5o9u3 j1TGZuTteNDCC7+Qy+ZfdnifWh4f7QDZSKw9c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=FP8Z1na2izuqXXKsvJGMpoSUa3tesdKhkqD3oYTIBJAHd5RSjfA+9jvOS/8qQDBNHB UDYzqnxgA9kSc0SHqpDFgfbGep8te74HWDuuTWtgph1gnlf0v1IiMErQht/vbAFKYt5e YQpLKMxNtm7QKtbWJdykhgpq7oTijl6UTTq7U= Received: by 10.142.156.19 with SMTP id d19mr1254244wfe.6.1244785669352; Thu, 11 Jun 2009 22:47:49 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id k2sm1305356rvb.4.2009.06.11.22.47.47 (version=SSLv3 cipher=RC4-MD5); Thu, 11 Jun 2009 22:47:48 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Fri, 12 Jun 2009 14:50:32 +0900 From: Pyun YongHyeon Date: Fri, 12 Jun 2009 14:50:32 +0900 To: Thomas Lotterer Message-ID: <20090612055032.GD72855@michelle.cdnetworks.co.kr> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A312517.9030206@lotterer.net> User-Agent: Mutt/1.4.2.3i 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 Reply-To: pyunyh@gmail.com 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 05:47:50 -0000 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. > vge0: Read request size : 512 bytes. > vge0: TLP payload size : 128 bytes. > miibus0: on vge0 > vge0: Ethernet address: 00:40:63:xx:xx:xx > vge0: [FILTER] > vge0: link state changed to UP > vge0: watchdog timeout > vge0: unable to stop Rx/Tx MAC(0x09)! > vge0: soft reset timed out > vge0: link state changed to DOWN > vge0: link state changed to UP > > And this time a link has been established > > # 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. > > 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. > Hmm, you have a PCIe variant hardware and I remembers someone also told a couple of issues on his VT6130 controller. These days it's hard to find stand-alone PCI/PCIe controllers. If I manage to buy VT6130 controller I'll see what's going on.