Date: Wed, 21 Mar 2007 10:15:49 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-drivers@freebsd.org Cc: Jonas =?iso-8859-1?q?Andr=E9n?= <jonas@tullinge.mine.nu> Subject: Re: problem with bge nic. Message-ID: <200703211015.50099.jhb@freebsd.org> In-Reply-To: <000001c765e3$43c8c080$cb5a4180$@mine.nu> References: <000001c765e3$43c8c080$cb5a4180$@mine.nu>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <Broadcom BCM5704 B0, ASIC rev. 0x2100> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200703211015.50099.jhb>