From owner-freebsd-current@FreeBSD.ORG Tue Aug 10 19:50:12 2010 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 8C9311065673; Tue, 10 Aug 2010 19:50:12 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 48C5A8FC12; Tue, 10 Aug 2010 19:50:11 +0000 (UTC) Received: by pxi17 with SMTP id 17so245701pxi.13 for ; Tue, 10 Aug 2010 12:50:11 -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=Cvrq8A0dh+YTcAzjjeApR++u6QQ7xNIx3Yg9IfN7+5Y=; b=FYqYqczL7hu0TS5599rd4i8TLeHzWKoP6CEve6JKlAjqk9odHwNNY8VU41SpWVjH17 l3RU7jp4He5BjaasVZFy4/Mtt3/7UMNiNQleWe+JqeWbDWdyXFZn8gdfooWw38xp5HpP h6iAMqQuIC/sdwYqODtZC7FODQRpRfcaHQIvU= 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=BIe2gzPdwtGfoqEmHtKErWJLhSp/bkc34q4MrWHVA39owJleqD6mkNgm29xZSUWgIK LyIw5vGJtN9vv9/QxBDZkiCYkouM92tzuc/iwm8ueRAp3iogkHJ64JGsdI9cEy7YH7rG 0w+GBc2VR+MG6kaOo0KisdFewo77CeTI+3FEU= Received: by 10.142.140.19 with SMTP id n19mr15395127wfd.271.1281469811688; Tue, 10 Aug 2010 12:50:11 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id d4sm6464028wfh.11.2010.08.10.12.50.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 10 Aug 2010 12:50:09 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 10 Aug 2010 12:50:08 -0700 From: Pyun YongHyeon Date: Tue, 10 Aug 2010 12:50:08 -0700 To: Jeremy Chadwick Message-ID: <20100810195008.GF6960@michelle.cdnetworks.com> References: <10F0535B998A4923BF9CFD85DF936473@multiplay.co.uk> <20100810100414.GA31621@icarus.home.lan> <20100810105722.GA32407@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100810105722.GA32407@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Net , FreeBSD Current , Steven Hartland , Jack Vogel , FreeBSD stable Subject: Re: Watchdog resets on 82575 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: Tue, 10 Aug 2010 19:50:12 -0000 On Tue, Aug 10, 2010 at 03:57:22AM -0700, Jeremy Chadwick wrote: > On Tue, Aug 10, 2010 at 11:23:26AM +0100, Steven Hartland wrote: > > Thanks Jeremy, from that we get:- > > > > igb0@pci0:1:0:0: class=0x020000 card=0x060015d9 chip=0x10c98086 rev=0x01 hdr=0x00 > > vendor = 'Intel Corporation' > > class = network > > subclass = ethernet > > cap 01[40] = powerspec 3 supports D0 D3 current D0 > > cap 05[50] = MSI supports 1 message, 64 bit, vector masks > > cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled > > cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x4(x4) > > igb1@pci0:1:0:1: class=0x020000 card=0x060015d9 chip=0x10c98086 rev=0x01 hdr=0x00 > > vendor = 'Intel Corporation' > > class = network > > subclass = ethernet > > cap 01[40] = powerspec 3 supports D0 D3 current D0 > > cap 05[50] = MSI supports 1 message, 64 bit, vector masks > > cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled > > cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x4(x4) > > > > I assume there is a way to convert from the hex values to the human value > > but not sure what it is? > > The "card" and "chip" identifiers are part of the PCI ID specification. > You can see what the "human value" is by examining the source code for > the driver. Sometimes it's easy to figure out, other times there's a > series of #define's which you have to reverse engineer. > > In this case, there's two places with relevant information: > > src/sys/dev/e1000/if_igb.c > src/sys/dev/e1000/e1000_hw.h > > You have to split the Chip ID into two separate 16-bit portions, so > 0x10c9 and 0x8086. > > 0x8086 is Intel's vendor code. 0x10c9 is the device ID of the > individual NIC/model type. So: > > $ grep -i 0x10c9 * > e1000_hw.h:#define E1000_DEV_ID_82576 0x10C9 > > For Jack: igb_vendor_info_array should really be extended to include > actual ASCII strings for the individual chips/models/codenames. I'm > sure that's on your todo list somewhere. I'd be willing to write this > but would need a list of the models (or maybe the Linux driver has them > in comments, etc. and I could go off of that). > I guess em(4)/igb(4)/ixgb(4)/ixgbe(4) only shows vendor string and driver version which effectively hides controller name/model details in device attach phase. Personally I like to see more detailed controller model information which may help narrowing down affected lits of controllers when an issue is reported. Currently we have to get this information by requesting the output of pciconf(4) which in turn requires one more round trip of mail.