From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 19 13:53:16 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C55D1065670 for ; Sun, 19 Dec 2010 13:53:16 +0000 (UTC) (envelope-from martgross42@yahoo.de) Received: from nm10-vm0.bullet.mail.ird.yahoo.com (nm10-vm0.bullet.mail.ird.yahoo.com [77.238.189.90]) by mx1.freebsd.org (Postfix) with SMTP id F18BA8FC0A for ; Sun, 19 Dec 2010 13:53:15 +0000 (UTC) Received: from [77.238.189.231] by nm10.bullet.mail.ird.yahoo.com with NNFMP; 19 Dec 2010 13:38:51 -0000 Received: from [212.82.108.112] by tm12.bullet.mail.ird.yahoo.com with NNFMP; 19 Dec 2010 13:38:51 -0000 Received: from [127.0.0.1] by omp1021.mail.ird.yahoo.com with NNFMP; 19 Dec 2010 13:38:51 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 199930.7473.bm@omp1021.mail.ird.yahoo.com Received: (qmail 8400 invoked by uid 60001); 19 Dec 2010 13:38:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.de; s=s1024; t=1292765931; bh=7JsvktIhkfxPFJWSGtzMNYdUJaNpD+/7yLqVcHKKgfs=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=39vCyQwywCbp+Grp+njEfSDy/wKUokX/ZAVmc2veZamvqYHASx6finMRFVCjhM5WjqeLbcrjVpxvrxiSwfVYNap6G4z0+2kbI1G5GywMQWYl1UPWAqz9RHs2ALcD6c2garOVc/uBmFLI5xmX3ndTIgOmlmogJm/YK3mb4057LOM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=J5PWYOYp8MoESsQ7Pqj9V5HdW4tgW3JK+e3EByDTPdVUPXpb8k5hMh9gHPpbUDAjPBG6Eyf5agLoHNSDKxXEQHIbRwEdQu08dd0mRLp18RfjjvpSA9uHplrcqS/z5UuKG4ePbaJf0oPaxjZFIslITtccUCck4zBvi+g86rp3zQQ=; Message-ID: <77833.7343.qm@web29217.mail.ird.yahoo.com> X-YMail-OSG: mrEpzAgVM1ntwDOawN9YgfdQ8rxxER0OVuv98qFP6pbpPQY 23gtBGlXsu.0DNmr2gefGGo6ewy3cCWYW5L5GXHI52gd1IBHeERlHO5UNqHB ZuVtaJRjMnwP7H607uDUe0oRVJ7lDiEolTdhiO3CXL_.DDs8m95o6g4PKal. 61DIDMpe5oxnHMGNMW61ZxxQpSZkIb0izYSuMHwzqGuVlO82H1fajDaW_e5A AhyVtyK_hsz4uPh57jFLlT_e4Uz0hck2Hp1ElxF9tJkZ5ocpsR443sXpVVg. KVl9.2O1lh3LVPvPF8StR.Kb2hOUSRTh6JmWhtqUQWlcDI2RSTrq0LeIlmba 6bGGKm5zpK3._kM2Py32MBlNP1BL6RKxz02t2DNWVeJPRAXnmgS5jm3O0KZg Xp1j0IqHhtYNePv4.S6nVcQ7c_G4PU6_GtksgAZmzF9AKe9OuCouBzHl4GPx YNDpuleOrh4AY7YzBgKi9zrlE56_02vCJUkomT4TRg3jN595pzaiSKzkmGnr JBLtoxUmW64A- Received: from [84.155.9.91] by web29217.mail.ird.yahoo.com via HTTP; Sun, 19 Dec 2010 13:38:50 GMT X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.107.285259 Date: Sun, 19 Dec 2010 13:38:50 +0000 (GMT) From: Martin Gross To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: VIA Fire II Firewire Card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2010 13:53:16 -0000 Hi all, I got myself a Firewire Card (PCMCIA) with the mentioned VIA Fire II chipse= t. According to the manpage this chip is supported by Freebsd. However, whe= n i plug in the card, syslog tells me the following: fwohci0: port 0x1080-0x10ff mem 0xbfed0000-0xbfed07f= f,0xbfed1000-0xbfed10ff irq 16 at device 0.0 on cardbus0 fwohci0: [ITHREAD] fwohci0: OHCI version 0.0 (ROM=3D0) fwohci0: invalid OHCI version fwohci0: fwohci_init failed with err=3D6 device_attach: fwohci0 attach returned 5 This was reproduceable with 9.0-current and 8.1-release. Also tested the card under windows and linux, there it worked, so I can rul= e out that the card is broken. Linux tells me that the OHCI version is 1.10= which sounds a bit more reasonable. I'll provide dumps / traces or what ever is necessary to debug this. I'm th= ankful for every hint. thx Martin =0A=0A From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 20 05:31:43 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6E7F106566C for ; Mon, 20 Dec 2010 05:31:43 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from imr-mb01.mx.aol.com (imr-mb01.mx.aol.com [64.12.207.164]) by mx1.freebsd.org (Postfix) with ESMTP id 849E58FC0C for ; Mon, 20 Dec 2010 05:31:43 +0000 (UTC) Received: from imo-ma03.mx.aol.com (imo-ma03.mx.aol.com [64.12.78.138]) by imr-mb01.mx.aol.com (8.14.1/8.14.1) with ESMTP id oBK5VZs3031303; Mon, 20 Dec 2010 00:31:35 -0500 Received: from dieterbsd@engineer.com by imo-ma03.mx.aol.com (mail_out_v42.9.) id c.df5.1263b5c2 (45324); Mon, 20 Dec 2010 00:31:31 -0500 (EST) Received: from smtprly-ma02.mx.aol.com (smtprly-ma02.mx.aol.com [64.12.207.141]) by cia-mc04.mx.aol.com (v129.7) with ESMTP id MAILCIAMC048-5c4c4d0eea3110b; Mon, 20 Dec 2010 00:31:30 -0500 Received: from web-mmc-d03 (web-mmc-d03.sim.aol.com [205.188.103.93]) by smtprly-ma02.mx.aol.com (v129.5) with ESMTP id MAILSMTPRLYMA022-5c4c4d0eea3110b; Mon, 20 Dec 2010 00:31:29 -0500 To: martgross42@yahoo.de Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Dec 2010 00:31:29 -0500 X-AOL-IP: 67.206.170.189 X-MB-Message-Source: WebUI Received: from 67.206.170.189 by web-mmc-d03.sysops.aol.com (205.188.103.93) with HTTP (WebMailUI); Mon, 20 Dec 2010 00:31:29 -0500 MIME-Version: 1.0 From: dieterbsd@engineer.com X-MB-Message-Type: User Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailer: Mail.com Webmail 33053-STANDARD Message-Id: <8CD6E1E49F8720F-778-1C3C@web-mmc-d03.sysops.aol.com> X-Spam-Flag: NO X-AOL-SENDER: dieterbsd@engineer.com Cc: freebsd-firewire@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: VIA Fire II Firewire Card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2010 05:31:43 -0000 Martin writes: > fwohci0: port 0x1080-0x10ff mem=20 0xbfed0000-0xbfed07ff,0xbfed1000-0xbfed10ff irq 16 at device 0.0 on\ cardbus0 > fwohci0: [ITHREAD] > fwohci0: OHCI version 0.0 (ROM=3D0) > fwohci0: invalid OHCI version > fwohci0: fwohci_init failed with err=3D6 > device_attach: fwohci0 attach returned 5 I have an onboard VIA, on FreeBSD 8.0/amd64 I get fwohci0: port 0xa800-0xa87f mem=20 0xfdffe000-0xfdffe7ff irq 18 at device 6.0 on pci1 fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=3D1) fwohci0: No. of Isochronous channels is 4. My chip is actually a 6307 but reported as 6306. I think the only difference is one chip has 2 ports and the other has 3. > Linux tells me that the OHCI version is 1.10 which sounds a bit more=20 reasonable. And matches what FreeBSD reports for my chip. So most likely your card=20 is actually version 1.10 but FreeBSD is reading it incorrectly. Perhaps an address=20 mapping problem? Unfortunately I can't actually use this controller due to PR=20 kern/113785. :-( From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 20 21:38:13 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3E7C106566B for ; Mon, 20 Dec 2010 21:38:12 +0000 (UTC) (envelope-from martgross42@yahoo.de) Received: from nm13-vm0.bullet.mail.ird.yahoo.com (nm13-vm0.bullet.mail.ird.yahoo.com [77.238.189.195]) by mx1.freebsd.org (Postfix) with SMTP id 5AC038FC08 for ; Mon, 20 Dec 2010 21:38:11 +0000 (UTC) Received: from [77.238.189.233] by nm13.bullet.mail.ird.yahoo.com with NNFMP; 20 Dec 2010 21:38:11 -0000 Received: from [212.82.108.242] by tm14.bullet.mail.ird.yahoo.com with NNFMP; 20 Dec 2010 21:38:11 -0000 Received: from [127.0.0.1] by omp1007.mail.ird.yahoo.com with NNFMP; 20 Dec 2010 21:38:11 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 212093.70073.bm@omp1007.mail.ird.yahoo.com Received: (qmail 53343 invoked by uid 60001); 20 Dec 2010 21:38:11 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.de; s=s1024; t=1292881091; bh=LGQz7MUwEAopT2fMxwasIYfsrCNcOP1Liriru42Lg6Q=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=rzpxwIj+hcQfrbuewffAxTdpznBFwljYTz490uHqi8cays3xWpxhCFMt0L+StiI/dnw1bQK4RN8FGr5wAD9GlcOsr57OI9F/9dOdlHXUDjbNvcmAipXd+aGZvbdd80BzEHvWImFxqO8oKwRRsHIjBGp9dwDKlRNsvkm8i1W3+5k= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Vhh/OOrLvg1jd4haykbvZHWAkuo0wU8xSZZgOJRNCa/gxD65trqCWFUyUWMgfqNaC8r8a9OsicgmqkxHs4gRE0zNvJ+jg9sd3a984NUzGKqcI4rC/iigLGBLfwivwD3FpVOYI5KEBScjxm3AUG2a+q9OoWA02L1KvigpFggLhAA=; Message-ID: <113718.52586.qm@web29201.mail.ird.yahoo.com> X-YMail-OSG: 8DmUftwVM1nSqMPZxv.dtWk_tw1INV95DVsRW1tcgH.9MEG 3lCUFQTDb1H4NkBGUEAHS8RgF7c7iyPwPtUQ91WFiirHKctcSofkHRNKabOK ZdG6VMoqSXRqPfbI46gl9WBYaIxb2G3aGGpew9N.vQJKfBckSaqYghM4h8O2 XTu1IjFMkDZkHaqdIcmTm4E9fvlURLcsLRBIz3CyLo64UyPfKAv0bd8cXhji dHZuvsxV0PPKUf6E- Received: from [84.155.24.110] by web29201.mail.ird.yahoo.com via HTTP; Mon, 20 Dec 2010 21:38:10 GMT X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.107.285259 Date: Mon, 20 Dec 2010 21:38:10 +0000 (GMT) From: Martin Gross To: dieterbsd@engineer.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-firewire@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: VIA Fire II Firewire Card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2010 21:38:13 -0000 Hi,=0A=0A>> fwohci0: port 0x1080-0x10ff mem =0A0xbfe= d0000-0xbfed07ff,0xbfed1000-0xbfed10ff irq 16 at device 0.0 on\=0Acardbus0= =0A>> fwohci0: [ITHREAD]=0A>> fwohci0: OHCI version 0.0 (ROM=3D0)=0A>> fwoh= ci0: invalid OHCI version=0A>> fwohci0: fwohci_init failed with err=3D6=0A>= > device_attach: fwohci0 attach returned 5=0A=0A=0A>> Linux tells me that t= he OHCI version is 1.10 which sounds a bit more =0Areasonable.=0A=0A> And m= atches what FreeBSD reports for my chip.=A0 So most likely your card is act= ually version 1.10 but FreeBSD is reading it incorrectly.=A0 Perhaps an add= ress mapping problem?=0A=0AThis is what I'm thinking, but I have no idea wh= ere to start with. Any suggestions?=0A=0A=0A=0A=0A From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 24 23:07:06 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D34E11065670; Fri, 24 Dec 2010 23:07:06 +0000 (UTC) (envelope-from jan.koum@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5A2928FC19; Fri, 24 Dec 2010 23:07:06 +0000 (UTC) Received: by qyk36 with SMTP id 36so7081293qyk.13 for ; Fri, 24 Dec 2010 15:07:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=G1X9KC6+eWILcy89mcqm160Y48i5NdZMuAMIZADu/iE=; b=haekRCHNecGttakH3E6lVHx9lsnLOMLwE4KACToQ85ZxaNN6YycnAjgpoPhzxKTavW hR8/yC3GZGu1xgyUKTwijUj4DBtJADj0H+XBk/yeubrX9RHsMs8I2HQWjNq9Q2wcJem6 hteBNSf3pEFq3B1nFn58jsgox/nvnpd+mEQV8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=F0kX7Kw+m7+VmlegUp+dH4Zgx0FMy6Hro9VZMRugOluJZYaEXsGqrDri/ISXex/zfJ KDkySJarvdrqNQmvBEtpw/fyK7ztFDERNZpyI6LRyJ6UrJS0t/3lq/yuikDzXxnyWLG+ oauSzNKGUeKAKuiTz4omH48RoGb3dP4UHqI/o= MIME-Version: 1.0 Received: by 10.229.187.199 with SMTP id cx7mr8506328qcb.132.1293230671009; Fri, 24 Dec 2010 14:44:31 -0800 (PST) Sender: jan.koum@gmail.com Received: by 10.229.241.211 with HTTP; Fri, 24 Dec 2010 14:44:30 -0800 (PST) In-Reply-To: References: <1290533941.3173.50.camel@home-yahoo> <4CEC0548.1080801@sentex.net> Date: Fri, 24 Dec 2010 14:44:30 -0800 X-Google-Sender-Auth: 38AsrF8lzP7uUU_DiMZZxLWiSKo Message-ID: From: Jan Koum To: Ivan Voras , Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-net@freebsd.org" , Jack Vogel , Sean Bruno , "freebsd-hardware@freebsd.org" Subject: Re: em driver, 82574L chip, and possibly ASPM X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2010 23:07:06 -0000 hi Ivan and Mike, wanted to follow up and see if you found a solid long-term solution to this bug. we are still seeing this problem in our 8.2 environment with ASPM already disabled. here is what we have: 1. motherboard is SuperMicro X8SIE-LN4F Intel Xeon: em0@pci0:3:0:0: class=0x020000 card=0x040d15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' class = network subclass = ethernet em1@pci0:4:0:0: class=0x020000 card=0x040d15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' class = network subclass = ethernet em2@pci0:5:0:0: class=0x020000 card=0x040d15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' class = network subclass = ethernet em3@pci0:6:0:0: class=0x020000 card=0x040d15d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' class = network subclass = ethernet 2. ASPM is already disabled in the BIOS 3. when em1 interface locks up, sysctl debug says: Interface is NOT RUNNING and INACTIVE em1: hw tdh = 0, hw tdt = 0 em1: hw rdh = 0, hw rdt = 0 em1: Tx Queue Status = 0 em1: TX descriptors avail = 110 em1: Tx Descriptors avail failure = 319 em1: RX discarded packets = 0 em1: RX Next to Check = 80 em1: RX Next to Refresh = 80 4. doing "ifconfig em1 down; sleep1; ifconfig em1 up" resolves the issue and removes OACTIVE flag from em1. 5. we are running 8.2-PRERELEASE from December 19th: % grep '$FreeBSD' /usr/src/sys/dev/e1000/if_em.c /*$FreeBSD: src/sys/dev/e1000/if_em.c,v 1.21.2.18 2010/12/14 19:59:39 jfv Exp $*/ dmesg output is: em1: port 0xcc00-0xcc1f mem 0xfb4e0000-0xfb4fffff,0xfb4dc000-0xfb4dffff irq 17 at device 0.0 on pci4 em1: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfb4e0000 em1: Reserved 0x4000 bytes for rid 0x1c type 3 at 0xfb4dc000 em1: attempting to allocate 3 MSI-X vectors (5 supported) msi: routing MSI-X IRQ 259 to local APIC 0 vector 53 msi: routing MSI-X IRQ 260 to local APIC 0 vector 54 msi: routing MSI-X IRQ 261 to local APIC 0 vector 55 em1: using IRQs 259-261 for MSI-X em1: Using MSIX interrupts with 3 vectors em1: [MPSAFE] em1: [ITHREAD] em1: [MPSAFE] em1: [ITHREAD] em1: [MPSAFE] em1: [ITHREAD] em1: bpf attached em1: Ethernet address: 00:25:90:0e:25:e9 aside from running cronjob every minute to check for dead interface and reset it, is there anything else we can try? thanks. On Tue, Nov 23, 2010 at 10:36 AM, Jack Vogel wrote: > 82574 is supposed to be em, not igb :) Its always had this kind of > 'in-between' > status, it was targeted as a 'client' or consumer part, but it has MSIX > which > make it almost like 8257[56]. > > Mike, there are some further 82574 changes to shared code that I'm looking > into today. > > Jack > > > On Tue, Nov 23, 2010 at 10:17 AM, Mike Tancsa wrote: > > > On 11/23/2010 12:39 PM, Sean Bruno wrote: > > > On Tue, 2010-11-23 at 04:47 -0800, Ivan Voras wrote: > > >> It looks like I'm unfortunate enough to have to deploy on a machine > > >> which has the 82574L Intel NIC chip on a Supermicro X8SIE-F board, > which > > > igb0@pci0:5:0:0: class=0x020000 card=0x8975152d chip=0x10c98086 > > > > Strange, the 82574 attaches as em for me, not igb > > > > em1@pci0:10:0:0: class=0x020000 card=0x34ec8086 chip=0x10d38086 > > rev=0x00 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' > > class = network > > subclass = ethernet > > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) > > cap 11[a0] = MSI-X supports 5 messages in map 0x1c > > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > > ecap 0003[140] = Serial 1 001517ffffed68a4 > > > > Normally, its msix, but I had disabled that hoping it would fix the > problem > > > > em1: port 0x2000-0x201f mem > > 0xb4100000-0xb411ffff,0xb4120000-0xb4123fff irq 16 at dev > > ice 0.0 on pci10 > > em1: Using an MSI interrupt > > em1: [FILTER] > > em1: Ethernet address: 00:15:17:ed:68:a4 > > > > > > ---Mike > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org > " > From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 24 23:21:11 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CB71106564A; Fri, 24 Dec 2010 23:21:11 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id AE7598FC0A; Fri, 24 Dec 2010 23:21:10 +0000 (UTC) Received: by qwj9 with SMTP id 9so7138305qwj.13 for ; Fri, 24 Dec 2010 15:21:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=hL+ACW00U2D5STmjwAGOtnAKP21h3hqvQzQ/jfjjFtM=; b=mEfN1vvUjHHc1gymt5Nzi33tUujDu7XmioVC9JPbkhVZU6TGGLr25SiuTI0jDzCnYt JH/Zz1CWxhkR0TpAxqgmZb6PQGr5fh0QUwKAqEDzuMBfhPRTFM7mSyvtIliU8LSLyubp R3z4hc1dDGfdTpDBbN0L3Crmn50HINbplDAJ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=XGv217BbMA0SQH3G1ACAMyOWPPu7rDpyRsZDibONTjRWosfGtrzpK1QWdbo+IAGwaC QFyx0h5rxIrjXVcvbGgLVqobH9WTy8CErw3bA8m/HOlmFiqhUnWaRnumnmjgCedTE9Hu fwS7Q1a+EJrHrNXY1Tbi5mzb+Nq9L1KkMkIiA= Received: by 10.229.246.79 with SMTP id lx15mr8919094qcb.25.1293232869620; Fri, 24 Dec 2010 15:21:09 -0800 (PST) MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.229.44.70 with HTTP; Fri, 24 Dec 2010 15:20:29 -0800 (PST) In-Reply-To: References: <1290533941.3173.50.camel@home-yahoo> <4CEC0548.1080801@sentex.net> From: Ivan Voras Date: Sat, 25 Dec 2010 00:20:29 +0100 X-Google-Sender-Auth: pChvIQdtL9ObqcF2JY0tCu4zJ6A Message-ID: To: Jan Koum Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-net@freebsd.org" , "freebsd-hardware@freebsd.org" , Jack Vogel , Mike Tancsa Subject: Re: em driver, 82574L chip, and possibly ASPM X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2010 23:21:11 -0000 On 24 December 2010 23:44, Jan Koum wrote: > > hi Ivan and Mike, > wanted to follow up and see if you found a solid long-term solution to th= is > bug.=C2=A0we are still seeing this problem in our 8.2 environment with AS= PM > already disabled. =C2=A0here is what we have: Hi, The patches Jack made when this discussion was ongoing helped both me and AFAIK Mike also. The machine I had which exhibited these problems now works fine and stable. The patches should have been MFCed, but just in case - try the version from 9-current. During testing, I've also found that the BIOS setting "Remap PCI memory" or "Remap device memory" or something like that (I can't look it up now) also helps if disabled. Mike AFAIK didn't have this setting in his machine's BIOS. From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 25 02:19:29 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75CF7106566C; Sat, 25 Dec 2010 02:19:29 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 07F878FC0C; Sat, 25 Dec 2010 02:19:28 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:5570:ff31:c40c:8eac] ([IPv6:2607:f3e0:0:4:5570:ff31:c40c:8eac]) by smarthost1.sentex.ca (8.14.4/8.14.4) with ESMTP id oBP2JQmh036316 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 24 Dec 2010 21:19:26 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4D1554A7.5000507@sentex.net> Date: Fri, 24 Dec 2010 21:19:19 -0500 From: Mike Tancsa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Jan Koum References: <1290533941.3173.50.camel@home-yahoo> <4CEC0548.1080801@sentex.net> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on IPv6:2607:f3e0:0:1::12 Cc: "freebsd-net@freebsd.org" , Sean Bruno , Jack Vogel , Ivan Voras , "freebsd-hardware@freebsd.org" Subject: Re: em driver, 82574L chip, and possibly ASPM X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Dec 2010 02:19:29 -0000 On 12/24/2010 5:44 PM, Jan Koum wrote: > hi Ivan and Mike, > > wanted to follow up and see if you found a solid long-term solution to this > bug. we are still seeing this problem in our 8.2 environment with ASPM > already disabled. here is what we have: Hmmm, With the latest version of the driver in RELENG_8 (its the same as in HEAD) I havent seen the problem. However, I would only see it once per week prior to that. The odd thing is that it would happen during a slightly lower than normal backup load, but almost always at the same time (early sunday AM). Not sure what would trigger it exactly. If it happened again, I was going to enable port mirroring on the switchport and capture the traffic, hoping some "special" pattern would enable the issue. Do you have IPMI enabled on the NIC ? I tried to turn it off on my MB, but there is no clear way to do this. It 'seems' to be off, but not sure if it really is. One thing I noticed was that when the NIC was hung, it still was able to receive and process IPMI commands from an external host. ---Mike > > 1. motherboard is SuperMicro X8SIE-LN4F Intel Xeon: > > em0@pci0:3:0:0: class=0x020000 card=0x040d15d9 chip=0x10d38086 rev=0x00 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' > class = network > subclass = ethernet > em1@pci0:4:0:0: class=0x020000 card=0x040d15d9 chip=0x10d38086 rev=0x00 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' > class = network > subclass = ethernet > em2@pci0:5:0:0: class=0x020000 card=0x040d15d9 chip=0x10d38086 rev=0x00 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' > class = network > subclass = ethernet > em3@pci0:6:0:0: class=0x020000 card=0x040d15d9 chip=0x10d38086 rev=0x00 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' > class = network > subclass = ethernet > > 2. ASPM is already disabled in the BIOS > > 3. when em1 interface locks up, sysctl debug says: > > Interface is NOT RUNNING > and INACTIVE > em1: hw tdh = 0, hw tdt = 0 > em1: hw rdh = 0, hw rdt = 0 > em1: Tx Queue Status = 0 > em1: TX descriptors avail = 110 > em1: Tx Descriptors avail failure = 319 > em1: RX discarded packets = 0 > em1: RX Next to Check = 80 > em1: RX Next to Refresh = 80 > > 4. doing "ifconfig em1 down; sleep1; ifconfig em1 up" resolves the issue and > removes OACTIVE flag from em1. > > 5. we are running 8.2-PRERELEASE from December 19th: > % grep '$FreeBSD' /usr/src/sys/dev/e1000/if_em.c > /*$FreeBSD: src/sys/dev/e1000/if_em.c,v 1.21.2.18 2010/12/14 19:59:39 jfv > Exp $*/ > > dmesg output is: > > em1: port 0xcc00-0xcc1f mem > 0xfb4e0000-0xfb4fffff,0xfb4dc000-0xfb4dffff irq 17 at device 0.0 on pci4 > em1: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfb4e0000 > em1: Reserved 0x4000 bytes for rid 0x1c type 3 at 0xfb4dc000 > em1: attempting to allocate 3 MSI-X vectors (5 supported) > msi: routing MSI-X IRQ 259 to local APIC 0 vector 53 > msi: routing MSI-X IRQ 260 to local APIC 0 vector 54 > msi: routing MSI-X IRQ 261 to local APIC 0 vector 55 > em1: using IRQs 259-261 for MSI-X > em1: Using MSIX interrupts with 3 vectors > em1: [MPSAFE] > em1: [ITHREAD] > em1: [MPSAFE] > em1: [ITHREAD] > em1: [MPSAFE] > em1: [ITHREAD] > em1: bpf attached > em1: Ethernet address: 00:25:90:0e:25:e9 > > aside from running cronjob every minute to check for dead interface and > reset it, is there anything else we can try? > > thanks. > > > On Tue, Nov 23, 2010 at 10:36 AM, Jack Vogel wrote: > >> 82574 is supposed to be em, not igb :) Its always had this kind of >> 'in-between' >> status, it was targeted as a 'client' or consumer part, but it has MSIX >> which >> make it almost like 8257[56]. >> >> Mike, there are some further 82574 changes to shared code that I'm looking >> into today. >> >> Jack >> >> >> On Tue, Nov 23, 2010 at 10:17 AM, Mike Tancsa wrote: >> >>> On 11/23/2010 12:39 PM, Sean Bruno wrote: >>>> On Tue, 2010-11-23 at 04:47 -0800, Ivan Voras wrote: >>>>> It looks like I'm unfortunate enough to have to deploy on a machine >>>>> which has the 82574L Intel NIC chip on a Supermicro X8SIE-F board, >> which >>>> igb0@pci0:5:0:0: class=0x020000 card=0x8975152d chip=0x10c98086 >>> >>> Strange, the 82574 attaches as em for me, not igb >>> >>> em1@pci0:10:0:0: class=0x020000 card=0x34ec8086 chip=0x10d38086 >>> rev=0x00 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = 'Intel 82574L Gigabit Ethernet Controller (82574L)' >>> class = network >>> subclass = ethernet >>> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >>> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >>> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) >>> cap 11[a0] = MSI-X supports 5 messages in map 0x1c >>> ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected >>> ecap 0003[140] = Serial 1 001517ffffed68a4 >>> >>> Normally, its msix, but I had disabled that hoping it would fix the >> problem >>> >>> em1: port 0x2000-0x201f mem >>> 0xb4100000-0xb411ffff,0xb4120000-0xb4123fff irq 16 at dev >>> ice 0.0 on pci10 >>> em1: Using an MSI interrupt >>> em1: [FILTER] >>> em1: Ethernet address: 00:15:17:ed:68:a4 >>> >>> >>> ---Mike >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>> >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org >> " >> > From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 25 23:28:06 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 610E0106564A; Sat, 25 Dec 2010 23:28:06 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from imr-da02.mx.aol.com (imr-da02.mx.aol.com [205.188.105.144]) by mx1.freebsd.org (Postfix) with ESMTP id 209ED8FC08; Sat, 25 Dec 2010 23:28:05 +0000 (UTC) Received: from imo-ma03.mx.aol.com (imo-ma03.mx.aol.com [64.12.78.138]) by imr-da02.mx.aol.com (8.14.1/8.14.1) with ESMTP id oBPNS53j027477; Sat, 25 Dec 2010 18:28:05 -0500 Received: from dieterbsd@engineer.com by imo-ma03.mx.aol.com (mail_out_v42.9.) id n.d4e.79a1c64a (37557); Sat, 25 Dec 2010 18:28:01 -0500 (EST) Received: from smtprly-ma02.mx.aol.com (smtprly-ma02.mx.aol.com [64.12.207.141]) by cia-mb03.mx.aol.com (v129.7) with ESMTP id MAILCIAMB036-5c4e4d167dfe1d0; Sat, 25 Dec 2010 18:28:01 -0500 Received: from web-mmc-m05 (web-mmc-m05.sim.aol.com [64.12.224.138]) by smtprly-ma02.mx.aol.com (v129.5) with ESMTP id MAILSMTPRLYMA024-5c4e4d167dfe1d0; Sat, 25 Dec 2010 18:27:58 -0500 To: freebsd-firewire@freebsd.org, freebsd-hardware@freebsd.org Content-Transfer-Encoding: quoted-printable Date: Sat, 25 Dec 2010 18:27:58 -0500 X-MB-Message-Source: WebUI X-AOL-IP: 67.206.163.150 X-MB-Message-Type: User MIME-Version: 1.0 From: dieterbsd@engineer.com Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailer: Mail.com Webmail 33069-STANDARD Received: from 67.206.163.150 by web-mmc-m05.sysops.aol.com (64.12.224.138) with HTTP (WebMailUI); Sat, 25 Dec 2010 18:27:58 -0500 Message-Id: <8CD72A27FE37E5A-B84-15C2E@web-mmc-m05.sysops.aol.com> X-Spam-Flag: NO X-AOL-SENDER: dieterbsd@engineer.com Cc: Subject: Re: VIA Fire II Firewire Card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Dec 2010 23:28:06 -0000 Do you have any other PCMCIA cards? If so do they work with FreeBSD? Have you tried a verbose boot? It gives slightly more data: fwohci0: port 0xa800-0xa87f mem=20 0xfdffe000-0xfdffe7ff irq 18 at device 6.0 on pci1 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xfdffe000 ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 53 fwohci0: [MPSAFE] fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=3D1) fwohci0: No. of Isochronous channels is 4. Looking through the code: /usr/src/sys/dev/firewire/fwohci.c: fwohci_init(struct fwohci_softc=20 *sc, device_t dev) I suspect that sc contains bogus data, in particular: bus_space_tag_t bst; bus_space_handle_t bsh; It might be useful to add a printf in fwohci_init() to display the=20 values for bst and bsh.