From owner-freebsd-drivers@FreeBSD.ORG Wed Mar 21 15:46:41 2007 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E9D816A406 for ; Wed, 21 Mar 2007 15:46:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 3495713C4C6 for ; Wed, 21 Mar 2007 15:46:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l2LFkdcu055977; Wed, 21 Mar 2007 10:46:39 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Wed, 21 Mar 2007 10:15:49 -0400 User-Agent: KMail/1.9.6 References: <000001c765e3$43c8c080$cb5a4180$@mine.nu> In-Reply-To: <000001c765e3$43c8c080$cb5a4180$@mine.nu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200703211015.50099.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 21 Mar 2007 10:46:39 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2892/Wed Mar 21 05:40:09 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Jonas =?iso-8859-1?q?Andr=E9n?= Subject: Re: problem with bge nic. X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2007 15:46:41 -0000 On Tuesday 13 March 2007 10:48:37 pm Jonas Andr=E9n wrote: > Hi, >=20 > I have a little problem, I just got a hold of an IBM NetXtreme Broadcom > dualport NIC (5704C). > But I cant get it to work in my freebsd-box, I don=92t actually know if i= t is > supposed to work in a 32-bit pci slot at all but I hope that maybe someone > on this mailinglist can clear that up for me :). >=20 > I am running FreeBSD 6.2-RELEASE-p2. >=20 > I get this message in dmesg: > bge0: mem 0xdf010000-0xdf01ffff i= rq > 16 at device 11.0 on pci2 > bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xdf010000 > bge0: firmware handshake timed out > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: chip initialization failed > device_attach: bge0 attach returned 6 >=20 > and it doesent even seem to find the second port of the NIC, atleast it > doesent recognice it as an Broadcom device but rather an Ethernet > controller: VSN Systemen BV Unknown device 1648 (rev 10) (prog-if 01). >=20 > Can someone bring some light to this problem? Try the driver from RELENG_6. Your second adapter has a hardware issue tho= ugh=20 (or maybe your motherboard does, try moving it to another slot maybe) as it= =20 has a couple of single-bit errors in the config space stuff which is why it= =20 wasn't probed and had a weird vendor: > pci2: physical bus=3D2 > found-> vendor=3D0x14e4, dev=3D0x1648, revid=3D0x10 > bus=3D2, slot=3D11, func=3D0 > class=3D02-00-00, hdrtype=3D0x00, mfdev=3D1 > cmdreg=3D0x0006, statreg=3D0x82b0, cachelnsz=3D8 (dwords) > lattimer=3D0x20 (960 ns), mingnt=3D0x40 (16000 ns), maxlat=3D0x00= (0 ns) > intpin=3Db, irq=3D10 > powerspec 2 supports D0 D3 current D0 > MSI supports 8 messages, 64 bit > map[10]: type 1, range 64, base df010000, size 16, enabled > pcib2: (null) requested memory range 0xdf010000-0xdf01ffff: good > pcib2: matched entry for 2.11.INTB > pcib2: slot 11 INTB hardwired to IRQ 16 > found-> vendor=3D0x15e4, dev=3D0x1648, revid=3D0x10 > bus=3D2, slot=3D11, func=3D1 > class=3D02-00-01, hdrtype=3D0x00, mfdev=3D1 > cmdreg=3D0x0106, statreg=3D0x82b0, cachelnsz=3D8 (dwords) > lattimer=3D0x21 (990 ns), mingnt=3D0x40 (16000 ns), maxlat=3D0x00= (0 ns) > intpin=3Dc, irq=3D16 > map[10]: type 1, range 64, base df010100, size 8, enabled > pcib2: (null) requested memory range 0xdf010100-0xdf0101ff: good > map[18]: type 1, range 32, base 00000100, size 8, enabled > map[1c]: type 1, range 32, base 00000100, size 8, enabled > map[20]: type 1, range 32, base 00000100, size 8, enabled > map[24]: type 1, range 32, base 00000100, size 8, enabled > pcib2: matched entry for 2.11.INTC > pcib2: slot 11 INTC hardwired to IRQ 17 Note when comparing these two entries that you have a vendor of 0x15e4 rath= er=20 than 0x14e4 (so 0x100 was set when it should have been clear). The BARs al= so=20 have 0x100 set when it should have been clear. The cmdreg and lattimer reg= s=20 also have the extra bit set. =2D-=20 John Baldwin