From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 27 06:27:29 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62A4916A4BF; Wed, 27 Aug 2003 06:27:29 -0700 (PDT) Received: from quelrod.quelrod.net (cs679135-141.austin.rr.com [67.9.135.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B34544025; Wed, 27 Aug 2003 06:27:18 -0700 (PDT) (envelope-from quel@quelrod.net) Received: from quelrod.net (cs679135-141.austin.rr.com [67.9.135.141]) by quelrod.quelrod.net (8.12.9/8.12.6) with ESMTP id h7RDRZ0E002691; Wed, 27 Aug 2003 08:27:35 -0500 (CDT) Received: from localhost (quel@localhost) by quelrod.net (8.12.9/8.12.9/Submit) with ESMTP id h7RDRYM2028213; Wed, 27 Aug 2003 08:27:35 -0500 (CDT) Date: Wed, 27 Aug 2003 08:27:34 -0500 (CDT) From: James Nobis To: "Kenneth D. Merry" In-Reply-To: <20030827131039.GA17250@panzer.kdm.org> Message-ID: References: <009c01c36c6e$7a882150$4bc8a8c0@orac> <20030827131039.GA17250@panzer.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: dcswest@gmx.net cc: freebsd-mobile@freebsd.org Subject: Re: bcm4400 driver and Dell 8500 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2003 13:27:29 -0000 On Wed, 27 Aug 2003, Kenneth D. Merry wrote: > On Wed, Aug 27, 2003 at 08:40:25 +0100, Duncan Barclay wrote: > > Hello James and Ken, > > > > Both of you are having real problems with the bcm driver and both of you > > have a Dell 8500. > > > > This is James' dmesg output, which from memory looks very similar to your > > Ken? > > > > > bcm0: mem 0xfaffe000-0xfaffffff irq 11 > > > at device 0.0 on pci2 > > > bcm0: Ethernet address: ff:ff:ff:ff:ff:ff > > > panic: bcm0: Strange type for core 0xffffffff > > Yep, the messages I get are identical when I load it as a module. > > > > I'm running 5.1-current from august 22nd. I can try pulling down the > > > latest 5.1 tommorow if you think this might help. This is the same result > > > as when I tried the driver from over a month ago. > > > > We think that the problem is something to do with the PCI configuration of > > the machine. The ethernet address being ff:ff:ff:ff:ff:ff indicates that the > > memory map is not right. > > > > > Before sending this email I was going to obtain a backtrace. I recompiled > > > with the symbol table and kernel debugger and now the driver appears to > > > work fine. Should it work this way? > > > > Hmm interesting. Ken can you try this and see if the driver then works? > > I've already got the kernel debugger on. Do you mean changing the module > compile somehow so that more symbols are included? (It seems to resolve > the function addresses in the module fine.) > compiling with options DDB and makeoptions DEBUG=-g is what i mean > The stack trace from the module load is: > > panic() > bcm_chip_get_core() > bcm_chip_reset() > bcm_attach() > device_probe_and_attach() > etc. > > If I boot a kernel with the bcm driver compiled in, and don't attach to the > docking station, it comes up fine until I insert my fxp card in the carbus > slot. Then I get the panic in bcm_ring_rx_eof() that I reported last > night. FWIW, when I have the driver compiled in, the memory location is > identical to location used when the module loads (above), but the ethernet > address is properly decoded: > > bcm0: mem 0xfaffe000-0xfaffffff irq 11 at device 0.0 on pci2 > bcm0: Ethernet address: 00:0b:db:94:bf:42 > miibus0: on bcm0 > > If I boot a kernel with the bcm driver compiled in, and don't attach to the > docking station, and don't insert my fxp card, I get slightly further. I > tried running dhclient, and got: > > All mbufs or mbuf clusters exhausted, please see tuning(7). > bcm0: initialization failed: no memory for rx buffers > > Then I tried just manually ifconfiging the interface, and it works! > > Here's what netstat -m says: > > {erebor:/usr/home/ken:1:0} netstat -nm > mbuf usage: > GEN cache: 0/0 (in use/in pool) > CPU #0 cache: 576/608 (in use/in pool) > Total: 576/608 (in use/in pool) > Mbuf cache high watermark: 512 > Maximum possible: 34304 > Allocated mbuf types: > 576 mbufs allocated to data > 1% of mbuf map consumed > mbuf cluster usage: > GEN cache: 0/0 (in use/in pool) > CPU #0 cache: 575/584 (in use/in pool) > Total: 575/584 (in use/in pool) > Cluster cache high watermark: 128 > Maximum possible: 17152 > 3% of cluster map consumed > 1320 KBytes of wired memory reserved (98% in use) > 1 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > Performance, once I manually assigned an address seems okay; I was able to > ftp a file over from another machine at a little over 11MB/sec. > > If I insert the fxp card after the bcm driver is configured, the cardbus > initialization fails, and then I get the following messages over and over > again: > > "eek j=6, macCurrent 511, con288" > > At that point I can 't even break into the debugger. > > That's all the time I have for tinkering with it this morning... > > Looks like things are working somewhat better, but there is still some > weird stuff going on... > > Ken > -- > Kenneth Merry > ken@kdm.org > I don't have a docking station. The built in ethernet is which uses the bcm driver. I only have used it as a module and have not tried otherwise. -James