Date: Wed, 27 Aug 2003 21:03:33 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: James Nobis <quel@quelrod.net> Cc: dcswest@gmx.net Subject: Re: bcm4400 driver and Dell 8500 Message-ID: <20030828030333.GA24120@panzer.kdm.org> In-Reply-To: <Pine.BSO.4.53.0308271223120.9473@quelrod.net> References: <Pine.BSO.4.53.0308262257210.24387@quelrod.net> <009c01c36c6e$7a882150$4bc8a8c0@orac> <20030827131039.GA17250@panzer.kdm.org> <Pine.BSO.4.53.0308270823360.19094@quelrod.net> <1062000128.717.4.camel@gyros> <Pine.BSO.4.53.0308271223120.9473@quelrod.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 27, 2003 at 12:24:11 -0500, James Nobis wrote: > > > On Wed, 27 Aug 2003, Joe Marcus Clarke wrote: > > > On Wed, 2003-08-27 at 09:27, James Nobis wrote: > > > 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: <Broadcom 10/100 Base-T Ethernet> 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 > > > > Note, on my 5150, I also have a kernel built with -g. I do not have DDB > > compiled in, but I have never tried a kernel without -g. I may be > > susceptible to the same "all-ffs" problem. > > > > Joe > > When i just did a -g, it still would crash when i tried to load the Ahh. I've had DDB on the whole time, but I've found that I don't get a crash (i.e. the all ff's problem) if I don't have my fxp card plugged in when I load the bcm module. dhclient doesn't cause the system to run out of mbufs, but then again it hangs. If I ifconfig the interface manually things work fine. Ken -- Kenneth Merry ken@kdm.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030828030333.GA24120>