From owner-freebsd-stable@FreeBSD.ORG Thu Dec 14 04:13:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16F6B16A415 for ; Thu, 14 Dec 2006 04:13:31 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A3FE43C9F for ; Thu, 14 Dec 2006 04:11:57 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so124171ana for ; Wed, 13 Dec 2006 20:13:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PJJuzJW3Er36oLNJJ85R5IpM0rAyr1o24LrKNp9velSN2io4tSx07ntTFCO2dOAHJ4w5BzS+6H9uZkXmsmQ1cbGUQS+/JS/yff/Mgb2zjrdtniVoKvBBGjuEfI/jCGlCDmsBysvgUHyqQ6rl5FJXTNSnr1LSgFhpzbFI+Q9XMqs= Received: by 10.100.58.4 with SMTP id g4mr452773ana.1166069609246; Wed, 13 Dec 2006 20:13:29 -0800 (PST) Received: by 10.100.112.17 with HTTP; Wed, 13 Dec 2006 20:13:29 -0800 (PST) Message-ID: <2a41acea0612132013r63b8b2a8q21be60a37cc7728b@mail.gmail.com> Date: Wed, 13 Dec 2006 20:13:29 -0800 From: "Jack Vogel" To: "Chris Buechler" In-Reply-To: <4580B356.2030501@chrisbuechler.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <457EDD6B.20107@chrisbuechler.com> <2a41acea0612120936q671d5b59g39100983f2adf9db@mail.gmail.com> <457FA268.4020003@chrisbuechler.com> <2a41acea0612131238p34222362qde6ae51b18055744@mail.gmail.com> <4580B356.2030501@chrisbuechler.com> Cc: freebsd-stable@freebsd.org Subject: Re: 6.2-RC1 em(4) issue - freezes during CD boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2006 04:13:31 -0000 On 12/13/06, Chris Buechler wrote: > Jack Vogel wrote: > > I need the PCI ID of that NIC, just to be sure that I can't reproduce > > this, but > > I doubt it, pciconf -l > > > Here's the pciconf -l from 6.2-RC1, custom kernel (copy of GENERIC, > minus 'device em') > > agp0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x700c1022 rev=0x20 > hdr=0x00 > pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x700d1022 rev=0x00 > hdr=0x01 > isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x74401022 rev=0x05 > hdr=0x00 > atapci0@pci0:7:1: class=0x01018a card=0x74411022 chip=0x74411022 > rev=0x04 hdr=0x00 > none0@pci0:7:3: class=0x068000 card=0x74431022 chip=0x74431022 rev=0x03 > hdr=0x00 > none1@pci0:8:0: class=0x030000 card=0x00000000 chip=0x47581002 rev=0x01 > hdr=0x00 > none2@pci0:9:0: class=0x020000 card=0x002e8086 chip=0x100e8086 rev=0x02 > hdr=0x00 > asr0@pci0:10:0: class=0x0e0001 card=0xc0661044 chip=0xa5011044 rev=0x01 > hdr=0x00 > pcib2@pci0:10:1: class=0x060400 card=0x00000068 chip=0xa5001044 > rev=0x01 hdr=0x01 > pcib3@pci0:16:0: class=0x060400 card=0x00000000 chip=0x74481022 > rev=0x05 hdr=0x01 > ohci0@pci3:0:0: class=0x0c0310 card=0x00000000 chip=0x74491022 rev=0x07 > hdr=0x00 > xl0@pci3:8:0: class=0x020000 card=0x246610f1 chip=0x920010b7 rev=0x78 > hdr=0x00 > > > > interesting question is what will happen when you load > > the em driver afterwords :) > > Indeed, I was expecting Bad Things to happen. But no, after the > kldload, the interface was detected, I put an IP on it and it's working > fine. I bound an iperf server to that interface and ran an iperf client > from a slower box with a gig card and got ~520 Mbps out of it (probably > limited by the slower client box). So it seems to be working fine as > long as it's not compiled into the kernel. Granted I haven't done any > really extensive testing or use of it. > > Here's the pciconf -l after loading the em driver. > > agp0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x700c1022 rev=0x20 > hdr=0x00 > pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x700d1022 rev=0x00 > hdr=0x01 > isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x74401022 rev=0x05 > hdr=0x00 > atapci0@pci0:7:1: class=0x01018a card=0x74411022 chip=0x74411022 > rev=0x04 hdr=0x00 > none0@pci0:7:3: class=0x068000 card=0x74431022 chip=0x74431022 rev=0x03 > hdr=0x00 > none1@pci0:8:0: class=0x030000 card=0x00000000 chip=0x47581002 rev=0x01 > hdr=0x00 > em0@pci0:9:0: class=0x020000 card=0x002e8086 chip=0x100e8086 rev=0x02 > hdr=0x00 > asr0@pci0:10:0: class=0x0e0001 card=0xc0661044 chip=0xa5011044 rev=0x01 > hdr=0x00 > pcib2@pci0:10:1: class=0x060400 card=0x00000068 chip=0xa5001044 > rev=0x01 hdr=0x01 > pcib3@pci0:16:0: class=0x060400 card=0x00000000 chip=0x74481022 > rev=0x05 hdr=0x01 > ohci0@pci3:0:0: class=0x0c0310 card=0x00000000 chip=0x74491022 rev=0x07 > hdr=0x00 > xl0@pci3:8:0: class=0x020000 card=0x246610f1 chip=0x920010b7 rev=0x78 > hdr=0x00 This is quite odd, and as a matter of fact, because our test group is always testing drivers that are made here at Intel, I believe most often they have the driver as a module and not static... hmmm, so let me see if I have any luck reproducing it. Since its often the case that a kernel you rebuild is NOT the same as the one install ends you with it might be a good test to go ahead, redefine em back into the kernel and see if THAT new kernel hangs. Just be SURE and keep this other kernel available to boot up again :) I"ll look into this, but not right away, I have a high priority chunk of code I'm working on and that needs to get done in the next couple days, and then I'm having a couple long-needed weeks of vacation :) Happy Holidays, Jack